opus version correction

This commit is contained in:
bastien
2026-04-03 18:08:21 +02:00
parent fa50c0f402
commit f8811fab37
24 changed files with 1005 additions and 1068 deletions
+3 -1
View File
@@ -1,7 +1,9 @@
---
name: analyze
description: Analyze code or a codebase deeply before any modification
description: Deep factual code analysis — read-only, no solutions proposed
argument-hint: <code, file, or area to analyze>
disable-model-invocation: true
allowed-tools: Read, Grep, Glob, Bash
---
Load and follow strictly:
-15
View File
@@ -1,15 +0,0 @@
---
name: git-pr
description: Analyze all changes on the current branch since it diverged from base (retroactive across sessions), create logical commits, push, and open a draft PR/MR. Works with GitHub, GitLab, Gogs, and Gitea. Never merges — creates a draft for user validation.
argument-hint: [PR title or leave empty for auto-detection]
disable-model-invocation: true
allowed-tools: Read, Bash, Grep, Glob
---
Load and follow strictly:
- .claude/agents/git-workflow.md
Execute the GIT WORKFLOW on the current repository.
User context (optional title or instructions):
$ARGUMENTS
+18
View File
@@ -0,0 +1,18 @@
---
name: health
description: Run setup diagnostic — check symlinks, plugins, permissions, token budget
argument-hint: (no arguments needed)
disable-model-invocation: true
allowed-tools: Bash
---
Run the health check script and report findings to the user:
```bash
bash ~/.claude/doctor.sh
```
After displaying the output:
- If errors are found, suggest the specific fix commands shown in the output.
- If only warnings, note them but confirm the setup is functional.
- If all checks pass, confirm the setup is healthy.
+4 -40
View File
@@ -1,6 +1,6 @@
---
name: init-project
description: Initialize a complete project from scratch. Plugin check → interview → analyze → design → validate → scaffold skeleton → plan v1 features → validate plan → implement (TDD, subagents) → analyze → review → finish. Same implementation rigor as ship-feature.
description: Full project init: interview → design → scaffold → implement (TDD). Two validation gates.
argument-hint: <project idea or description>
disable-model-invocation: true
allowed-tools: Read, Write, Edit, Bash, Grep, Glob
@@ -35,42 +35,7 @@ $ARGUMENTS
---
### STEP 0a — BRANCH SETUP
Load the BRANCH SETUP section from: `.claude/agents/git-workflow.md`
Before anything else, ensure we are NOT on a protected branch.
```bash
git branch --show-current
```
**If on `main`, `master`, `develop`, or any protected branch:**
Derive a branch slug from the initial request:
- Take the first 3–4 meaningful words
- Lowercase, hyphen-separated
- Max 50 chars
```bash
git fetch origin
git pull origin <current> --ff-only 2>/dev/null || true
git checkout -b feature/<project-slug>
```
Print: `✅ Working branch created: feature/<project-slug>`
**If already on a feature branch:**
Run the CONFLICT-SAFE REBASE procedure from git-workflow.md
to sync with main before starting.
Print: `✅ Branch: <current> (synced with main)`
**Do not proceed until the branch is clean and ready.**
---
### STEP 0b — PLUGIN CHECK
### STEP 0 — PLUGIN CHECK
Load and follow: `.claude/agents/plugin-advisor.md`
@@ -88,7 +53,7 @@ B) Type "force" to proceed without them
================================================================
```
**STOP. Wait for user response.**
- Re-run → restart from STEP 0b
- Re-run → restart from STEP 0
- "force" → note missing plugins, continue to STEP 1
**If `ACTION REQUIRED: NO`:**
@@ -341,8 +306,7 @@ SYNC mode — no stop required. The readme-updater:
## RULES
- Never skip STEP 0a — branch setup is mandatory. Never commit on main/master.
- Never skip STEP 0b — plugin check is mandatory.
- Never skip STEP 0 — plugin check is mandatory.
- Never skip STEP 1 — no assumptions about missing info.
- Never implement without explicit user approval at STEP 4.
- Never implement without explicit user approval at STEP 7.
+1 -1
View File
@@ -1,6 +1,6 @@
---
name: plugin-check
description: Check active plugins vs current project needs. Recommends enabling or disabling based on context signals (frontend, design, QA, deployment, multi-session, fast-evolving libs). Run before init-project or ship-feature on a new project type.
description: Audit active plugins vs project needs. Recommends enable/disable actions.
argument-hint: [project description or feature to build]
disable-model-invocation: true
allowed-tools: Read, Bash, Glob, Grep
+1 -1
View File
@@ -1,6 +1,6 @@
---
name: readme
description: Update the project README to reflect the current state of the codebase. Audits what is outdated, missing, or no longer accurate, then applies surgical updates. Preserves existing structure and style.
description: README audit — detect outdated sections, apply surgical updates
argument-hint: [what changed, feature name, or leave empty for full audit]
disable-model-invocation: true
allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+3 -1
View File
@@ -1,7 +1,9 @@
---
name: refactor
description: Improve code quality without changing behavior
description: Improve code quality without changing behavior — strict norm enforcement
argument-hint: <file, function, or module to refactor>
disable-model-invocation: true
allowed-tools: Read, Write, Edit, Grep, Glob, Bash
---
Load and follow strictly:
+4 -76
View File
@@ -1,6 +1,6 @@
---
name: ship-feature
description: Ship a feature end-to-end using the Superpowers workflow. Starts with a plugin check, then Brainstorm → Plan → Implement (subagent-driven) → Review → Finish branch.
description: Ship feature end-to-end: design → plan → implement (TDD) → review → finish
argument-hint: <feature description>
disable-model-invocation: true
allowed-tools: Read, Write, Edit, Bash, Grep, Glob
@@ -33,48 +33,7 @@ $ARGUMENTS
---
### STEP 0a — BRANCH SETUP
Load the BRANCH SETUP section from: `.claude/agents/git-workflow.md`
```bash
git branch --show-current
```
**If on `main`, `master`, `develop`, or any protected branch:**
Derive a branch slug from the feature request:
- Take the first 3–4 meaningful words from $ARGUMENTS
- Lowercase, hyphen-separated, max 50 chars
- Prefix with `feature/`
```bash
git fetch origin
git pull origin <current> --ff-only 2>/dev/null || true
git checkout -b feature/<feature-slug>
```
Print: `✅ Working branch created: feature/<feature-slug>`
**If already on a feature/bugfix/hotfix branch:**
Run the CONFLICT-SAFE REBASE procedure from git-workflow.md
to sync with the base branch before implementing.
Print: `✅ Branch: <current> (synced)`
**Special case — bugfix on a feature branch:**
If the user explicitly says "bugfix" or "fix" in the request AND
the current branch is a feature branch:
```bash
git checkout -b bugfix/<bug-slug>
```
Creates the bugfix branch FROM the feature branch — correct hierarchy.
**Do not proceed until the branch is clean.**
---
### STEP 0b — PLUGIN CHECK (mandatory gate)
### STEP 0 — PLUGIN CHECK (mandatory gate)
Load and follow: `.claude/agents/plugin-advisor.md`
@@ -105,7 +64,7 @@ Options:
```
Wait for user response.
- If user re-runs `/ship-feature` → start from STEP 0a again
- If user re-runs `/ship-feature` → start from STEP 0 again
- If user types "force" → note missing plugins and continue to STEP 1
**If the advisor output says `ACTION REQUIRED: NO`:**
@@ -198,40 +157,9 @@ SYNC mode — no stop required. The readme-updater:
---
### STEP 9 — CREATE PR (optional gate)
Ask the user:
```
================================================================
SHIP FEATURE — PR CREATION
================================================================
Feature is implemented, tested, and README is synced.
Create a PR/MR now?
yes → run /git-pr and open a draft PR
no → stop here, you can run /git-pr manually later
================================================================
```
**STOP — wait for user response.**
IF yes:
Load and follow: `.claude/agents/git-workflow.md`
The git-workflow agent will:
- Show all changes since branch start (retroactive)
- Propose a commit plan for approval
- Push and create a draft PR/MR on GitHub/GitLab/Gogs/Gitea
IF no:
Print: `✅ Feature shipped. Run /git-pr when ready to open a PR.`
Stop.
---
## RULES
- Never skip STEP 0a — branch setup is mandatory. Never implement on main/master.
- Never skip STEP 0b — plugin check is mandatory.
- Never skip STEP 0 — plugin check is mandatory.
- Never skip brainstorming.
- Never implement without explicit user approval of the plan.
- Keep subagents isolated — no shared context between tasks.