gurix/skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Replace honest-reviewer with code-review skill

Browse Source 
- Remove honest-reviewer (Socratic/devil's-advocate approach)
- Add code-review skill: high-precision review based on current best
  practices (confidence scoring >= 80, validate-before-report, context
  gathering beyond the diff, strict output contract, GLM/open-weight
  guardrails)
- dev-workflow: point review step at code-review, findings instead of
  questions; also adopt issue-based plan storage with explicit user
  approval gate
This commit is contained in:
Markus Graf
2026-09-28 21:42:01 +02:00
parent d22f69f47e
commit 2bce5799dc
3 changed files with 125 additions and 104 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dev/dev-workflow/SKILL.md
+4 -4
View File
@@ -22,19 +22,19 @@ Discuss the task, idea, or bug with the coding agent. The outcome is an **implem
- Summary of research and discussion
- Implementation plan broken into discrete steps
Save the plan in the feature branch as `{feature-slug}-plan.md`. The file is deleted when the workflow completes.
Create a GitLab/Git issue for the plan. The issue title starts with the feature slug, and the description contains the full plan. **WAIT for explicit user approval before creating the issue.**
### 2. Implementation
Before starting, the agent reads `AGENT.md` (project guidelines). Implementation proceeds step-by-step according to the plan. Each step is committed individually.
**Only proceed if the user explicitly approves the plan** (e.g., `go`, `approved`, `start`). Do not start implementing on your own. Before starting, the agent reads `AGENT.md` (project guidelines). Implementation proceeds step-by-step according to the plan. Each step is committed individually.
### 3. Review
After implementation is complete, a subagent with **fresh context** reviews the code and implementation using `honest-reviewer`.
After implementation is complete, a subagent with **fresh context** reviews the code and implementation using `code-review`.
### 4. Iteration
The agent answers the reviewer's questions and fixes any issues. This cycle continues until the reviewer subagent approves.
The agent fixes any findings the reviewer reported. This cycle continues until the reviewer subagent approves.
### 5. Merge Request