Stats
Actions
Tags
From claude-optimizer
Use when the user proposes a new feature, refactor, or non-trivial change in conversational language ("I want to add", "we should refactor", "feature request"). Files a GitHub issue, branches, fixes, opens a PR with `Closes
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-optimizer:cm-issue-driven-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This is the user's preferred development flow for non-trivial work. It eliminates the need to re-explain "do it the proper way" on every new repo. The plugin is always on; this skill applies in every project where it ships.
This is the user's preferred development flow for non-trivial work. It eliminates the need to re-explain "do it the proper way" on every new repo. The plugin is always on; this skill applies in every project where it ships.
The frontmatter description: is the contract. In short: fire when the user describes a problem in chat without a precise code instruction.
Examples that fire:
Examples that don't fire (use the off-ramps below):
foo to bar in x.ts:42." (precise instruction)===." (explicit "quick fix")Do the edit directly, commit if the user wants, and move on. Do not invoke this skill when:
gh CLI not available, or repo isn't a git repo.When skipping, say so once — "I'll do this directly without the issue/PR ceremony since it's a small fix" — so the user knows the workflow was considered and bypassed deliberately.
For non-trivial work that doesn't hit an off-ramp:
Invoke superpowers:brainstorming (or its substitute) to ask 1-2 sharp clarifying questions. Restate the problem in user-confirmable form. Don't write code yet. Get explicit user confirmation before proceeding.
gh issue create --title "<short imperative>" --body "<repro + acceptance>"
.github/ISSUE_TEMPLATE/ if present. The plugin ships canonical feature_request.md and bug_report.md templates with sections: TL;DR · Problem (or Repro) · Acceptance · Out of scope · Risk · Alternatives considered. Skip sections that don't apply for small features; keep "Acceptance" and "Out of scope" even on small issues since the cm-decompose / pr-preflight gates downstream rely on them.maingit checkout main
git pull
git checkout -b feat/<N>-<slug> # for features
git checkout -b fix/<N>-<slug> # for bug fixes
git checkout -b chore/<N>-<slug> # for non-functional work
Branch name references the issue number so PRs are traceable.
Implement the change. While doing so, honour the project's other auto-active skills:
cm-token-discipline — terse responses, no preamble/postamble.cm-secret-hygiene — never read or write sensitive files / values.cm-checkpoint — write meaningful state entries when crossing milestones.For multi-step features, use cm-checkpoint to keep TASKS.md current.
Run real verification before claiming done — see cm-quality-gate. The literal word "done" should not appear in your response without evidence (tests passed, manual exercise succeeded, output verified).
git push -u origin <branch>
gh pr create --title "<title>" --body "<body containing 'Closes #<N>'>"
Closes #<N> auto-closes the issue when the PR merges.Refs #<N> if the PR partially addresses the issue — the issue stays open for the remaining scope.Open the PR in the GitHub UI (or gh pr view <N> --web) and read the diff. The browser surfaces things git diff in the terminal misses (line wrapping, file structure, missing files).
gh pr merge <N> --squash --delete-branch
Use --squash unless the project's PR template specifies otherwise. --delete-branch keeps the remote tidy.
git checkout main
git pull
Now the next task can branch from a clean updated main.
If during the work you identify out-of-scope items ("we should also fix Y", "this exposes a related bug Z"), file each as its own GitHub issue immediately rather than only listing them in the PR description. Reference the parent issue in the new issues. This keeps the backlog actionable and matches the user's stated preference for "keep moving forward."
superpowers:brainstorming, cm-checkpoint, or cm-quality-gate. It orchestrates them.gh can't reach a remote, fall back to local branch + commit, and tell the user the issue/PR steps were skipped.main: good — that's the user's setup. Always branch first.cm-quality-gate). Fix on the same branch with a new commit, push, let CI re-run. Don't merge red.gh issue list --search), reference it instead of filing a duplicate. The branch and PR still proceed normally with Closes #<existing>.Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub gibouu/claude-optimizer --plugin claude-optimizer