feat: Add lint skill (zero-tolerance) + strengthen kickstart linting mandate
New skill: lint — zero-tolerance linting enforcement for all code changes. Detects project linter, fixes ALL violations, never disables rules. Updated kickstart: linting now explicit standing order #3 in worker template with "NON-NEGOTIABLE" language and zero-tolerance enforcement. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -205,12 +205,13 @@ You are now the **orchestrator**. Follow the protocol from `~/.claude/agent-guid
|
||||
|
||||
1. **All coding changes go through workers** — you NEVER edit source code directly
|
||||
2. **All coding changes require** code review, security review, and QA passing before completion
|
||||
3. **Completed issues are closed** in the repo via `~/.claude/scripts/git/issue-close.sh`
|
||||
4. **tasks.md is the single source of truth** — you are the sole writer
|
||||
5. **Branch from `develop`** (or whatever was detected/confirmed in Step 1) as the upstream
|
||||
6. **Max 2 parallel workers** at any time
|
||||
7. **Two-Phase Completion:** Bulk phase (target 90%), then Polish phase (target 100%)
|
||||
8. **Context threshold (55-60%):** Output handoff kickstart and STOP — do not compact
|
||||
3. **Linting is mandatory** — workers MUST run the project linter and fix ALL violations in files they touch. Zero lint errors. No disabling rules. No skipping files. This is non-negotiable.
|
||||
4. **Completed issues are closed** in the repo via `~/.claude/scripts/git/issue-close.sh`
|
||||
5. **tasks.md is the single source of truth** — you are the sole writer
|
||||
6. **Branch from `develop`** (or whatever was detected/confirmed in Step 1) as the upstream
|
||||
7. **Max 2 parallel workers** at any time
|
||||
8. **Two-Phase Completion:** Bulk phase (target 90%), then Polish phase (target 100%)
|
||||
9. **Context threshold (55-60%):** Output handoff kickstart and STOP — do not compact
|
||||
|
||||
### Orchestrator Loop
|
||||
|
||||
@@ -246,9 +247,14 @@ When spawning a worker, provide this structure:
|
||||
### Requirements
|
||||
{Issue description and acceptance criteria}
|
||||
|
||||
### Quality Gates
|
||||
Run these before reporting success:
|
||||
### Quality Gates (MANDATORY — zero tolerance)
|
||||
Run ALL of these before reporting success. Fix every failure.
|
||||
```
|
||||
{quality gate commands from project}
|
||||
```
|
||||
**Linting is NON-NEGOTIABLE.** Run the project linter and fix ALL violations
|
||||
in every file you touched. Do NOT leave lint warnings, do NOT disable rules,
|
||||
do NOT skip files. If you changed it, you lint it.
|
||||
|
||||
### Skills
|
||||
Read these before starting:
|
||||
|
||||
Reference in New Issue
Block a user