Skill: feature
Purpose
One command from idea to a merge-ready PR. The skill calibrates the ceremony
to the size of the change, drives everything autonomously, and surfaces
exactly two human decisions along the way: the interview answers (full path
only) and the review triage.
Step 1: Calibrate
Pick the lightest path that fits, announce it in one line, and proceed. The
user can override the choice at any time.
- trivial: typo, label, config tweak, a one-file fix with no behavior
risk. No spec, no issue. Branch and fix.
- standard: a small, well-described feature or bug with a clear scope.
No interview. Generate the GitHub issue directly from the user's
description (gh-issue conventions); the issue is the contract.
- full: anything non-trivial or ambiguous. Run the spec-interview
first; once the spec is validated, create the issue from it
automatically (gh-issue conventions), without a separate invocation.
Step 2: Build
- Branch
feat/<ref>-<slug> (or fix/<slug>) from an up-to-date default
branch.
- Implement, tests included. The flux-gate hooks run the gates on edits
and on push; a red gate is the normal fix loop, never something to
bypass.
- Local verification: run the
qa subagent whenever the change has
observable user flows. Run the reviewer subagent per the risk rule
(diff spanning many files or layers, schema or data migration,
sensitive area, spec with many criteria); skip it for small contained
changes. Rationale: documentation/walkthrough.md, part 2 step 5.
- Conventional commits,
git push -u origin HEAD.
Step 3: PR and CI
- Open the PR (gh-pr conventions: title, body from the real diff,
Closes #N when an issue exists, spec link, test plan).
- Watch CI and fix failures autonomously, capped at 3 attempts on the
same error.
Step 4: Review, on request, then triage
Nothing reviews the PR on its own, and there is no CI job to wait for:
when CI is green, tell the user the PR is ready and that a review is one
command away:
/flux:review
If the user asks for it now, run the review flow (diff the PR via the
pr-review subagent, post the findings as PR comments), and immediately
run the gh-address-comments flow: the comment-triage subagent assesses
each finding, you ask the user what to address in one question, fix the
retained items, reply on the comments, and bring CI back to green.
The triage is always human, never skipped. If the user does not request a
review in this session, hand over anyway (step 5): nothing is lost,
/flux:review then /flux:gh-address-comments handle it later.
Step 5: Hand over
Report the PR URL and CI status, plus the triage outcome if a review
happened in this session. Merging belongs to the user. Post-merge
lifecycle (spec status flip, index update, branch deletion) is automated
by the repository workflows, not by you.
Never
Merge, approve, bypass a gate, or address review comments without the
triage.
1---2name: feature3description: The single entry point to build anything. Calibrates the process to the change (trivial, standard or full), then drives it end to end (spec, issue, implementation, gates, PR, CI, review triage). Only merging stays human. Use when the user asks to implement, fix or build something.4---56# Skill: feature78## Purpose910One command from idea to a merge-ready PR. The skill calibrates the ceremony11to the size of the change, drives everything autonomously, and surfaces12exactly two human decisions along the way: the interview answers (full path13only) and the review triage.1415## Step 1: Calibrate1617Pick the lightest path that fits, announce it in one line, and proceed. The18user can override the choice at any time.1920- **trivial**: typo, label, config tweak, a one-file fix with no behavior21 risk. No spec, no issue. Branch and fix.22- **standard**: a small, well-described feature or bug with a clear scope.23 No interview. Generate the GitHub issue directly from the user's24 description (gh-issue conventions); the issue is the contract.25- **full**: anything non-trivial or ambiguous. Run the spec-interview26 first; once the spec is validated, create the issue from it27 automatically (gh-issue conventions), without a separate invocation.2829## Step 2: Build30311. Branch `feat/<ref>-<slug>` (or `fix/<slug>`) from an up-to-date default32 branch.332. Implement, tests included. The flux-gate hooks run the gates on edits34 and on push; a red gate is the normal fix loop, never something to35 bypass.363. Local verification: run the `qa` subagent whenever the change has37 observable user flows. Run the `reviewer` subagent per the risk rule38 (diff spanning many files or layers, schema or data migration,39 sensitive area, spec with many criteria); skip it for small contained40 changes. Rationale: `documentation/walkthrough.md`, part 2 step 5.414. Conventional commits, `git push -u origin HEAD`.4243## Step 3: PR and CI44451. Open the PR (gh-pr conventions: title, body from the real diff,46 `Closes #N` when an issue exists, spec link, test plan).472. Watch CI and fix failures autonomously, capped at 3 attempts on the48 same error.4950## Step 4: Review, on request, then triage5152Nothing reviews the PR on its own, and there is no CI job to wait for:53when CI is green, tell the user the PR is ready and that a review is one54command away:5556```57/flux:review58```5960If the user asks for it now, run the `review` flow (diff the PR via the61`pr-review` subagent, post the findings as PR comments), and immediately62run the gh-address-comments flow: the `comment-triage` subagent assesses63each finding, you ask the user what to address in one question, fix the64retained items, reply on the comments, and bring CI back to green.6566The triage is always human, never skipped. If the user does not request a67review in this session, hand over anyway (step 5): nothing is lost,68`/flux:review` then `/flux:gh-address-comments` handle it later.6970## Step 5: Hand over7172Report the PR URL and CI status, plus the triage outcome if a review73happened in this session. Merging belongs to the user. Post-merge74lifecycle (spec status flip, index update, branch deletion) is automated75by the repository workflows, not by you.7677## Never7879Merge, approve, bypass a gate, or address review comments without the80triage.
sbnet