Issue Spec Review
Testing & Qualityissue-spec-reviewIssue Spec Review is an Agent Skill for testing & quality published in the higress-group/higress repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Review an issue-spec implementation PR, create PR line findings, reply after fixes, and sync REVIEW comments.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/higress-group/higress/blob/HEAD/.claude/skills/issue-spec-review/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/issue-spec-review, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Issue Spec Review
Use when the user asks for /issue-spec:review, issue-spec review, or a PR review gate for an issue-spec implementation.
Steps
- Run issue-spec review sync --repo higress-group/higress --pr --implement --id REVIEW- --json to capture current rationale comments, findings, and checks.
- For non-trivial PRs, spawn or assign dedicated review agents as review PROCESS owners. Multiple review agents can run in parallel when their review scopes are independent.
- Give each review agent a concrete scope and expected output: actionable findings only, severity, file/line, linked SPEC, owner PROCESS, and suggested fix.
- Create actionable PR line findings with issue-spec review finding. Use P0/P1 for blockers and P2 for non-blocking follow-up.
- Assign every finding to a PROCESS owner. If no findings are found, record that result in REVIEW or VERIFY evidence.
- After the worker fixes a finding, reply to the original thread with issue-spec review reply --status resolved.
- Re-run review sync. P0/P1 findings must be resolved before final verify/archive.
Review DAG Policy
- Every non-trivial PR should have at least one dedicated review PROCESS node before final verify.
- Use multiple review agents in parallel when scopes are independent, for example CLI/API behavior, workflow docs, tests, compatibility, or security-sensitive surfaces.
- A review agent reports findings only; the coordinator converts actionable line findings into issue-spec review finding comments.
- P0/P1 findings block final verify until the owner PROCESS fixes them and issue-spec review reply records the resolution on the original thread.
- If a review agent finds no issues, record that result in REVIEW or VERIFY evidence before marking the review PROCESS done.