feat(spec-review, spec-revise): emit review file + add revise skill - #9
Open
ops-gaurav wants to merge 1 commit into
Open
feat(spec-review, spec-revise): emit review file + add revise skill#9ops-gaurav wants to merge 1 commit into
ops-gaurav wants to merge 1 commit into
Conversation
spec-review now writes the full audit to spec/<spec>/reviews/<phase>-review.md with stable R-XX issue IDs and unresolved checkboxes; the in-chat reply shrinks to a 150-250 word pointer at the file. spec-revise is new: it reads the latest review file, prompts the user to apply all P0/P1 fixes or walk through each issue, edits the phase doc, bumps a Revision/Updated header, and flips resolved checkboxes in the review file for a per-cycle audit trail. Ported across the anthropic, openai-codex, and cursor adapters; spec-approve notes updated to point at spec-revise for pre-approval fixes. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
1 participant
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.
Summary
spec-reviewnow writes a navigable review file atspec/<spec>/reviews/<phase>-review.md(overwrite each run; history in git). The file holds every issue — not just the top 5 — with stable IDs (R-01,R-02, …) and unresolved checkboxes that the new revise skill consumes. The in-chat reply shrinks to a 150–250-word summary pointing at the file.spec-reviseskill (anthropic, openai-codex, cursor) — takes a phase argument (requirements|design|research|tasks), reads the latest review file (disambiguates if multiple exist), asks per-run whether to apply all P0/P1 fixes or walk through each issue, edits the phase doc, bumps a**Revision:** N · **Updated:** YYYY-MM-DDheader at the top, and flips resolved checkboxes in the review file with a_(resolved in revision N on YYYY-MM-DD)_suffix.## Referencesblock intact.Unreleasedupdated.spec-approvenotes now point atspec-revisefor pre-approval fixes.Test plan
requirements.md, runspec-reviewphase=requirements → confirmspec/<spec>/reviews/requirements-review.mdis written with verdict, strengths, P0/P1/P2 issue groups, and stableR-XXIDs.spec-review→ confirm the file is overwritten (not appended).spec-revisephase=requirements with Apply all → confirm phase doc edits land, theRevision: 1 · Updated:header is inserted at the top, and- [ ]items flip to- [x]with the resolved-suffix in the review file.spec-reviseagain with no remaining open issues → confirm it stops cleanly and points at re-runningspec-review.spec-revisewith Walk through mode and tryyes/no/skipon different issues → confirm only approved fixes land and skipped ones stay unchecked.SKILL.md) and the cursor adapter (single.mdcwith inlined references) — same behavior described in the skill body.design,research, andtasksphases to confirm path parameterization works.🤖 Generated with Claude Code