Commit all working changes on the current branch, push to origin, and open a GitHub PR against main using the loaded spec for context. Adnan reviews and squash-merges manually on GitHub.
Scanned 9/4/2026
Install to Claude Code
Skills Directorynpx -y skills add NeverSight/skills_feed --skill feature-complete --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Feature Complete?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/neversight-feature-complete)More formats (shields.io, HTML) on the badges page.
---
name: feature-complete
description: Commit all working changes on the current branch, push to origin, and open a GitHub PR against main using the loaded spec for context. Adnan reviews and squash-merges manually on GitHub.
argument-hint: ["<type: PR title>"]
disable-model-invocation: true
---
# /feature-complete
Wraps up a feature: commits any uncommitted work, pushes the branch, and opens a PR. **Does not merge** — Adnan reviews and squash-merges on GitHub.
## Preconditions
1. **Must be on a feature branch**, not `main`. Verify with `git rev-parse --abbrev-ref HEAD`. If on `main`, refuse: `Cannot complete from main. Run /feature-load + /feature-start first.`
2. **`.claude/current-feature.md` should exist** for context. If missing, warn but proceed (the user may have run `git` commands manually).
## Steps
1. **Run the full validation suite** by invoking the same checks as `/feature-test`:
```bash
npm run typecheck && npm run lint && npm run build && npm run test && npm run test:e2e
```
**STOP** on any failure. Do not commit. Do not push. Surface the failure and tell the user to fix before re-running.
2. **Determine PR title.**
- If `$ARGUMENTS` is provided, use it. Must match `^(feat|fix|chore|docs|refactor|perf|style|test|build|ci): .+$`, ≤72 chars.
- If `$ARGUMENTS` is empty, derive from `.claude/current-feature.md`'s `type` and `title` fields: `<type>: <title>` (lowercase first word, truncate to 72 chars).
3. **Commit any uncommitted changes.**
- `git status --porcelain` — if non-empty, stage + commit. Otherwise skip.
- Subject: the PR title (or a `chore: tidy up before PR` if these are last-minute fixups).
- Body: 1–3 bullets describing the final changes.
- **NEVER** add `Co-Authored-By: Claude …` or bot footers.
4. **Push the branch.**
```bash
git push -u origin HEAD
```
5. **Build the PR body.** Draw from the loaded spec + the diff vs main:
```markdown
## Summary
- <bullet — what the PR does, in plain English>
- <bullet — why, if not obvious from the spec>
- <bullet — any noteworthy implementation choice>
## Spec
<one-paragraph quote or summary of the spec from .claude/current-feature.md>
## Test plan
- [ ] `npm run test:all` passes
- [ ] (manual) <one or two feature-specific checks from the spec>
```
**NEVER** add a "🤖 Generated with Claude Code" footer.
6. **Open the PR.**
```bash
gh pr create --base main --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"
```
7. **Report the PR URL** in one line.
8. **Return to main.** Run `git switch main && git pull` so the working tree is clean for the next `/feature-load`.
9. **Clean up stale branches (local + remote).** Run `npm run clean:branches`. Two cleanup cases:
- **Local** — force-deletes any local branch whose origin counterpart is gone (typically previously-merged PRs; squash-merge creates a new commit on `main` so `git branch -d` doesn't recognize the merge and refuses; the upstream-gone signal is the strongest proof the work has landed).
- **Remote** — deletes any remote branch on `origin` whose PR is MERGED on GitHub. Belt-and-suspenders for the rare case auto-delete-on-merge didn't fire (setting was off when the PR merged, or the branch was re-pushed after merge).
The branch from the PR *just* opened is not stale yet — its remote is alive, its PR is open — so it survives this cleanup and will be reaped on the next `/feature-complete` after Adnan merges it.
## What this skill does NOT do
- Does not merge the PR — Adnan reviews and squash-merges on GitHub manually.
- Does not delete the local branch for the PR it just opened — the upstream is still alive. Cleanup happens on the *next* `/feature-complete` run, after Adnan has merged this PR.
- Does not delete `.claude/current-feature.md` — left in place until the next `/feature-load`.
- Does not approve its own PR (impossible on GitHub for the PR author anyway).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
