Add Reviews skill for local feedback and PR workflows - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Review on ArchCode
Problem and author intent
ArchDev has installable Rooms, Tasks, Jobs, and Agents skills, but no Reviews skill teaching an external coding agent to operate local browser review. The local code-review protocol differs from task-plan review: it serves an immutable snapshot, streams draft changes and final feedback, and closes after submission. An agent needs to preserve snapshot identity, reconcile comment edits/removals, and launch a fresh review after fixing code.
This skill centers that local feedback loop and covers the surrounding review workflow, GitHub access through the site, publication, and Jobs-managed PR remediation.
What changed
ghauthentication boundaries.Scope: CLI distribution, agent instructions, and CI only; no backend/frontend runtime changes. Users can install the skill and ask their coding agent to open local review and iterate on feedback without a Task, PR, or daemon.
Risk
Low to medium: executable changes mirror the existing bootstrap pattern, while instructions govern reviews, repository access, and publication. The skill distinguishes feedback from approval, public PR actions from local notes, and write-capable executable workflow nodes from guarded reviewer agents. Most of the change is instructions split into focused references; packaging remains together for independent installation.
Testing
Canonical packaging/bootstrap proof: tests/reviews-skill.sh, the complete script target. It crosses the real skills-manager process boundary for global and repository installs, checks packaged references, and runs the installed bootstrap against a fixture installer/CLI. Assertions cover cold installation, exact executable identity, reuse, upgrading an older CLI returning generic help, and failure without misleading stdout. This is not a live browser/OAuth/provider end-to-end proof.
Passed:
bash tests/reviews-skill.shgit diff --checkparseReviewWorkflow/compileReviewWorkflowimplementationAutomatic coverage:
.github/workflows/installer-smoke-test.yml→reviews-skill→bash tests/reviews-skill.sh, on PRs, main pushes, and manual dispatch. No Aster target exists in this public distribution repository; CI invokes the script directly without test filters or skips.Follow-ups and limitations
Live browser feedback, GitHub OAuth/repository installation, model execution, publication, and Windows bootstrap were not exercised. A browser-connected machine with authorized accounts and a controlled repository is needed to prove that full workflow; the new CI job covers packaging/bootstrap only. The workflow compiler check validates structure, not model outcomes. PowerShell bootstrap has no dedicated Reviews CI execution yet. No accounts, live automation, or production repositories were changed for validation.