jiazhizhong/higress
1
0
Fork 0
mirror of https://github.com/alibaba/higress.git synced 2026-07-23 21:00:41 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
main
higress/.agents/skills/issue-spec-review/SKILL.md
澄潭 d5f2b624fb feat: initialize issue-spec workflow for Higress (#4059) 
Signed-off-by: johnlanni <johnlanni@users.noreply.github.com>
Co-authored-by: johnlanni <johnlanni@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-04 21:55:53 +08:00

2.0 KiB
Raw Permalink Blame History

name, description, license, compatibility, metadata
name description license compatibility metadata
issue-spec-review Review an issue-spec implementation PR, create PR line findings, reply after fixes, and sync REVIEW comments. MIT Requires issue-spec CLI.
author version generatedBy
issue-spec 1.0 issue-spec

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

  1. Run issue-spec review sync --repo higress-group/higress --pr --implement --id REVIEW- --json to capture current rationale comments, findings, and checks.
  2. 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.
  3. Give each review agent a concrete scope and expected output: actionable findings only, severity, file/line, linked SPEC, owner PROCESS, and suggested fix.
  4. Create actionable PR line findings with issue-spec review finding. Use P0/P1 for blockers and P2 for non-blocking follow-up.
  5. Assign every finding to a PROCESS owner. If no findings are found, record that result in REVIEW or VERIFY evidence.
  6. After the worker fixes a finding, reply to the original thread with issue-spec review reply --status resolved.
  7. Re-run review sync. P0/P1 findings must be resolved before final verify/archive.

Review DAG Policy

  1. Every non-trivial PR should have at least one dedicated review PROCESS node before final verify.
  2. Use multiple review agents in parallel when scopes are independent, for example CLI/API behavior, workflow docs, tests, compatibility, or security-sensitive surfaces.
  3. A review agent reports findings only; the coordinator converts actionable line findings into issue-spec review finding comments.
  4. P0/P1 findings block final verify until the owner PROCESS fixes them and issue-spec review reply records the resolution on the original thread.
  5. If a review agent finds no issues, record that result in REVIEW or VERIFY evidence before marking the review PROCESS done.
Reference in New Issue View Git Blame Copy Permalink