Skip to content
Skills Library
Programming · Automation

finalize

/finalize

Use when implementation is done and the user wants to wrap it up: finalize, commit this, create a PR, ship it, or done implementing.

Licence
MIT
Last repository change
15.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 15.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when implementation is done and the user wants to wrap it up: finalize, commit this, create a PR, ship it, or done implementing.

Original author description

Use when implementation is done and the user wants to wrap it up: finalize, commit this, create a PR, ship it, or done implementing.

How it works

  1. 1. Policy and scope (before touching git)
  2. 2. Scan
  3. 3. Review the diff
  4. 4. Lint and test
  5. 5. Clean up
  6. 6. Stage and commit
  7. 7. Push and PR (only when asked)
  8. 8. Archive (after the commit succeeds)
  9. Quality bar
  10. Workflow context
Original SKILL.md headings · 136 lines, 895 words
SKILL.md preview
---
name: finalize
description: "Use when implementation is done and the user wants to wrap it up: finalize, commit this, create a PR, ship it, or done implementing."
---

# Finalize

Wrap up finished work: check, lint, test, clean up, commit, and only then the delivery steps the
user asked for. Nothing ships with failing checks, and nothing goes further than requested.

## 1. Policy and scope (before touching git)

- Read the repo's delivery policy: AGENTS.md / CLAUDE.md (a `## Ship policy` block if present),
  CONTRIBUTING, PR templates. It decides branch naming, commit format, whether commits go on a
  feature branch, PR base, and whether attribution trailers are allowed or required.
- Determine exactly which steps the user asked for: commit only, commit and push, open a PR, or
  merge. "Commit this" means a local commit. A bare "finalize" or "wrap it up" means lint, test,
  and a local commit, then ask before pushing or opening a PR. Merge only on an explicit request
  that the policy allows.
- If you are on the default branch and the policy (or the user's habit) requires a feature
  branch, create one before committing.
- Never add AI or tool attribution (co-author trailers, "generated with" footers) to commits or
  PRs unless the repo policy requires it.

Inputs, asked only if unclear: the feature or branch name, the PR base (from policy, else the
detected default branch), and files to exclude.

## 2. Scan

```bash
git status --short
git worktree list
DEFAULT=$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's@^origin/@@')
git branch --no-merged "${DEFAULT:-main}"
find . -path ./node_modules -prune -o \( -name '*.orig' -o -name '*.bak' -o -name '.DS_Store' \) -print
```

Report what you found before changing anything.

## 3. Review the diff

Read `git diff` for the files you will commit and fix: leftover debug output, commented-out code,
unused imports, to-do comments with no tracked follow-up, secrets or credentials, unrelated
changes. Only code in this change; pre-existing issues get mentioned, not fixed.

## 4. Lint and test

Use the commands the repo defines, in this order: project instructions, CI config,
`package.json` scripts, Makefile or task runner, the build tool's aggregate task (`./gradlew
check`, `mvn verify`). Fall back to a stack default only for tools the repo actually configures:

| Stack | Lint | Test |
|---|---|---|
| Java (Gradle / Maven) | configured Checkstyle, SpotBugs, or Spotless tasks | `./gradlew test` / `mvn test` |
| TypeScript / React | `npx eslint .` and `npx tsc --noEmit` | `npx vitest run` or `npx jest --ci` |
| Flutter / Dart | `dart analyze`, `dart format --set-exit-if-changed .` | `flutter test` |
| Android / Kotlin | configured ktlint or detekt | `./gradlew testDebugUnitTest` |
| E2E (if the change touches flows it covers) | - | `npx playwright test` |

Independent stacks can run in parallel. Show the real output with counts. Apply auto-fixes
(`eslint --fix`, formatters), fix the rest, and re-run until clean. Do not continue with lint
errors or failing tests.

## 5. Clean up

Destructive steps run only after the user confirms the list:
- Worktrees: `git worktree prune` drops entries whose directories are gone. Remove a worktree
  with `git worktree remove <path>` only when its branch is merged; never `rm -rf .worktrees/`.
- Branches: list `git branch --merged <default branch>` (excluding the current and default branch) and
  delete with `git branch -d` only the ones the user approves.
- Temp files from the scan, and `e2e/.captures.json`: delete after confirmation.
- Check `.gitignore` covers build output (`node_modules`, `target`, `build`, `.gradle`,
  `.dart_tool`).

## 6. Stage and commit

```bash
git add <specific paths>      # never git add -A or git add . blindly
git diff --cached --stat
```

Show the staged list. Exclude `.env`, credentials, keys, large binaries, build output.
Commit in the repo's format (default: Conventional Commits `<type>(<scope>): <description>`,
type from the change, scope from the main area touched).

## 7. Push and PR (only when asked)

Push the branch, then open the PR against the base from policy:

```bash
gh pr create --base <base> --title "<title>" --body "<body>"
```

Body: summary bullets, test results (actual counts), a design reference if a handoff manifest has
`stitch.project_id` or a `figma:` block, and the repo's PR template sections if it has one.
Return the PR URL. Do not merge unless the user asked for that too.

## 8. Archive (after the commit succeeds)

Follow the `handoff` lifecycle: archive only manifests whose `lifecycle.archivable_after` skills
have all consumed them.

```bash
ARCHIVE="claudedocs/.archive/$(date +%Y%m%d-%H%M%S)-<feature>"
mkdir -p "$ARCHIVE"
mv claudedocs/<feature>-*.md "$ARCHIVE/" 2>/dev/null
# design/ only after the user confirms nothing still uses it
```

Keep `claudedocs/handoff-*.yaml`, `e2e/test-plan.yaml`, `e2e/reports/`, and verification
screenshots. Make sure `claudedocs/.archive/` is ignored by git.

## Quality bar

- Lint clean and all tests passing, with real output shown
- Only intended files committed; no secrets, temp files, or build output
- Delivery went exactly as far as the user asked, in the repo's format and policy
- No orphaned worktrees or merged branches left behind (with the user's approval)

## Workflow context

- Follows `spec-to-impl`, `verify-impl`, or manual implementation work.
- Delivery only: verification of behavior belongs to `verify-impl`, a full review to `code-audit`.
- Feeds `release-notes` (PR description) and code review on the opened PR.

## Output contract
```yaml
produces:
  - type: git_commit
    ref: "<commit SHA>"
  - type: pull_request           # only when a PR was requested and created
    url: "<PR URL>"
    branch: "<branch name>"
  - type: evidence
    lint_output: "<actual linter stdout>"
    test_output: "<actual test runner stdout>"
    files_committed: ["<list>"]
    handoff: "Write claudedocs/handoff-finalize-<timestamp>.yaml - suggest: code-review, release-notes"
```

Versions

RepositoryScoreLicence
This page · omexit/claude-skills-pack100MIT
sentimony/agentic-workflow100MIT
grimoire-rs/grimoire100Apache-2.0
DnsQueen/orcinus-skills100MIT
educlopez/ui-craft100MIT
researai/deepscientist90Apache-2.0
alexiolan/craft-skills90GPL-3.0

Database snapshot: 13.11.2026 · package version e8ee1ce974c1 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100arn-shipping
    This skill should be used when the user says "shipping", "arness shipping", "ship it", "ship", "create PR", "open pull request", "push and PR", "commit and push", "wrap up", "ship the feature", "ship the fix", "ready to ship", "push changes", "finalize", "finish up", "done",…
  • 100finalize-task
    Use when a task worktree has passed validation - manually commits, merges, and cleans up, or prepares runner-owned commits and publication
  • 100hex-finalize
    Use when a review-approved feature branch is ready to land and the user asks to finalize it, tidy the commit series, or get the pull request ready to merge. Explicit invocation only — the merge itself stays the human's.
  • 100commit-push-pr
    Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
  • 95sa-finalize
    Finalize specification via Neo4j: statistics, glossary, ADR, traceability matrix, readiness assessment. All computed from graph queries.Use when: finalize spec with graph, generate statistics, or the user says "/nacl:sa-finalize".
  • 95nacl-sa-finalize
    Finalize specification via Neo4j: statistics, glossary, ADR, traceability matrix, readiness assessment. All computed from graph queries.Use when: finalize spec with graph, generate statistics, or the user says "/nacl-sa-finalize".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.