simplify
Use this skill after implementation and before testing to run a quality gate. Reviews changed files against the task document, checks maintainability standards, classifies plan deviations, and decides whether the work can proceed to verification.
How do I install this agent skill?
npx skills add https://github.com/eljun/claude-workflow-skills --skill simplifyIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill implements a quality gate process that analyzes task documents and source code for coding standards and security issues like hardcoded credentials. It is generally safe but lacks boundary markers for the external content it ingests, making it susceptible to indirect prompt injection.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
simplify - Quality Gate Stage
Invariants
- Review only the task scope and changed files.
- Do not add new product scope.
- Block major deviations before testing.
- Write durable findings to the task document.
- If the task doc has an
Implementation Notessection butTASKS.mdstill shows the row inPlannedorIn Progress, reconcile the row toTestingbefore continuing — implement ran but missed its tracker update. IfImplementation Notesis absent, do not reconcile; implement genuinely did not run and the user should be told.
Runtime adapters may expose this stage as a slash command, menu action, or natural-language skill invocation. The portable stage name is simplify.
Workflow
- Read
AGENTS.md. - Resolve the task ID and read
docs/task/{ID}-{task-name}.md. - Identify changed files from
Implementation Notesandgit diff --name-only. - Read changed files only.
- Check coding standards and maintainability.
- Compare implementation against requirements, file changes, out-of-scope boundaries, and acceptance criteria.
- Classify deviations.
- Append
Quality Gate Notesto the task document. - Return PASS or FAIL.
No Task Document
For a small change the user asked for directly, with no docs/task/ doc (a quick fix or polish):
- Review the diff (
git diffagainst the base branch) against the user's request instead of a task doc. - Apply the same standards checklist and deviation levels. "Scope" is what the user asked for.
- Record the result (
PASS/FAIL, findings, deviations) in the pull request body or the commit message, not in a new task doc. - Don't create
TASKS.mdrows for it unless the project asks for that.
Standards Checklist
Apply where relevant:
- no unused code, dead code, or commented-out implementation
- no broad
anyor untyped escape hatches when the project has typed alternatives - no deep nesting where guard clauses would be clearer
- functions and files have clear responsibility
- names describe behavior accurately
- repeated logic is extracted when repetition creates maintenance risk
- errors are handled intentionally
- no secrets, credentials, or debug logging in production paths
- tests that assert on old behaviour or wording are updated deliberately, with a comment saying why, never just deleted
- new or changed tests check behaviour or output where they can; a test that only asserts source text or structure is flagged as weak evidence
- every acceptance criterion in the task doc has a check that could fail; flag any that don't
- project conventions from
AGENTS.md,LEARNINGS.md, and the task doc are followed
Deviation Classification
| Level | Meaning | Outcome |
|---|---|---|
| Minor | Small implementation difference that still satisfies scope. | Document and proceed. |
| Medium | Meaningful difference that should be visible to the user. | Document and proceed only if risk is acceptable. |
| Major | Violates requirements, expands scope, or changes architecture without approval. | FAIL and stop. |
Output In Task Document
## Quality Gate Notes
### Result
PASS | FAIL
### Standards Review
- {Finding or "No blocking issues"}
### Deviations
- {Deviation level and rationale}
### Required Fixes
- {Only if FAIL}
Handoff
PASS:
Quality gate passed for task {ID}
Next stage: test {ID}
FAIL:
Quality gate failed for task {ID}
Return to implementation with the required fixes listed in the task document.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/eljun/claude-workflow-skills/simplify">View simplify on skillZs</a>