Publish multi-agent review findings from local JSON state to GitHub PR comments.
npx skills add https://github.com/joi-fairshare/agentic-workflow --skill postreview
Please help me install this Agent Skill. Skill: postReview Source: https://github.com/joi-fairshare/agentic-workflow/tree/main/skills/postReview Command: npx skills add https://github.com/joi-fairshare/agentic-workflow --skill postreview
This Skill removes the friction of manually copying multi-agent review findings into the GitHub UI by reading the saved ~/.agentic-workflow/<repo-slug>/reviews/<pr>.json state and publishing each agent’s comments in a single go.
/review and guards against reposting already published reviews unless explicitly approved.Use /postReview to publish the saved review state for PR 42 after /review finishes generating the local JSON file.
High-intent search queries and answers about installing and using this skill.
Posting multi-agent PR review comments to GitHub automatically is done by reading serialized local state files and batching each agent's inline and top-level issues into single review submissions via the GitHub API. This minimizes API calls while publishing all findings.
Yes, you can batch GitHub PR review submissions by bundling inline comments and top-level summaries into a single review per agent. This minimizes API calls while ensuring severity and focus metadata are captured in the published output.
Yes, postReview works by loading local JSON state files from the ~/.agentic-workflow/<repo>/reviews/<pr>.json path. It reads the stored multi-agent review findings and updates the same file with posted comment identifiers and timestamps for auditing.
The best way to sync local code review findings to GitHub is to use a state-sync tool that reads saved JSON files and pushes them as structured PR comments. This ensures the local state reflects what was sent to GitHub by storing posted review IDs.
To prevent reposting duplicate PR reviews to GitHub, the publishing process guards against reposting already published reviews unless explicitly approved. It checks the local state file for existing comment identifiers before submitting new GitHub API requests.
A limitation when publishing multi-agent reviews to GitHub PR comments is that it requires a pre-existing local state file generated by a prior review session. Without the ~/.agentic-workflow/<repo>/reviews/<pr>.json file, there is no data to publish.
dotnetPost and update unified PR review comments on GitHub via CLI.
bitwardenPost or update PR summary comments in GitHub Actions or local files.
aarushlohitOrchestrate multi-model code reviews across GitHub PRs and local environments.
Dev10x-GuruAudit merged GitHub Pull Requests for unresolved review threads and create follow-up issues.