creating-review-actionview-entry

Generate an ActionView pr-review-summary entry from a PowerReview session.

126|8|Updated May 5, 2023
One-click install
npx skills add https://github.com/MoaidHathot/Neovim-Moaid --skill creating-review-actionview-entry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-review-actionview-entry
Source: https://github.com/MoaidHathot/Neovim-Moaid/tree/main/config/Orchestra/Workspace/orchestrations/PullRequests/skills-actionview/creating-review-actionview-entry
Command: npx skills add https://github.com/MoaidHathot/Neovim-Moaid --skill creating-review-actionview-entry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of a structured ActionView entry for PR reviews by transforming a PowerReview session into a rich, navigable dashboard object that highlights per-comment details, author information, and review status.

Core Features & Use Cases

  • Converts consolidated PowerReview data into a pr-review-summary entry for ActionView.
  • Generates per-comment sections with metadata, justification text, code diffs, and actionable buttons (approve/delete).
  • Suitable for orchestration steps after all reviewers finish their drafts and the consolidated review is available.

Quick Start

Run the orchestration to generate the entry from a completed PowerReview session and push it to ActionView.

Frequently Asked Questions about creating-review-actionview-entry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a structured PR review summary from draft comments and code diffs?

To create a structured PR review summary, you can assemble pull request metadata, draft comments, and code diffs into a structured JSON payload that functions as a navigable dashboard object.

What is an ActionView entry in a code review workflow?

An ActionView entry is a structured JSON payload that highlights per-comment details, author information, and review status, transforming consolidated review data into a navigable dashboard object.

How do I automate pull request review consolidation after all reviewers finish drafts?

You can automate pull request review consolidation by running an orchestration step that transforms a completed PowerReview session into a pr-review-summary entry with actionable approve or delete buttons.

What required fields must be populated in a pr-review-summary JSON payload?

The required fields in a pr-review-summary JSON payload include schemaVersion, type, source, title, subtitle, severity, and per-comment details with draft IDs, ensuring action commands reference the correct PR URL.

Can I generate per-comment review sections with approve and delete actions?

Yes, you can generate per-comment sections containing metadata, justification text, code diffs, and actionable approve or delete buttons by assembling consolidated review data into a structured entry.

When should I generate an ActionView entry for a pull request review?

You should generate an ActionView entry after all reviewers finish their drafts and the consolidated review is available, ensuring all required PR metadata and code diffs are ready for the payload.