hai/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-05-18 02:22:04 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat: anti-skip rule for all review skills (v0.15.6.1) (#804)

Browse Source 
* feat: anti-skip rule for all review skills

Review skills sometimes skip sections when reviewing strategy or spec
plans. This adds an explicit anti-skip rule to CEO (1-11), eng (1-4),
design (1-7), and DX (1-8) review skills. Also fixes CEO header from
"10 sections" to "11 sections" to match actual count.

* chore: bump version and changelog (v0.15.6.1)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-04-04 21:22:40 -07:00
committed by GitHub
parent 8038cad4a7
commit 31943b2f02
10 changed files with 28 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
plan-eng-review/SKILL.md
View File

@@ -649,6 +649,8 @@ Always work through the full interactive review: one section at a time (Architec
## Review Sections (after scope is agreed)
**Anti-skip rule:** Never condense, abbreviate, or skip any review section (1-4) regardless of plan type (strategy, spec, code, infra). Every section in this skill exists for a reason. "This is a strategy doc so implementation sections don't apply" is always wrong — implementation details are where strategy breaks down. If a section genuinely has zero findings, say "No issues found" and move on — but you must evaluate it.
## Prior Learnings
Search for relevant learnings from previous sessions:

2
plan-eng-review/SKILL.md.tmpl
View File

@@ -114,6 +114,8 @@ Always work through the full interactive review: one section at a time (Architec
## Review Sections (after scope is agreed)
**Anti-skip rule:** Never condense, abbreviate, or skip any review section (1-4) regardless of plan type (strategy, spec, code, infra). Every section in this skill exists for a reason. "This is a strategy doc so implementation sections don't apply" is always wrong — implementation details are where strategy breaks down. If a section genuinely has zero findings, say "No issues found" and move on — but you must evaluate it.
{{LEARNINGS_SEARCH}}
### 1. Architecture review