Skip to content
Back to skills

Spec Finish

ASecurity

Post-implementation completion workflow. Use after spec-implement completes to validate, review, create stacked commits, and prepare for PR. Triggers when implementation is done, when the user says "finish", "done", "complete", or after implementation tasks are finished.

  • 46 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 26, 2026
developmentpythongobashcode-reviewgitapidocumentation

Works with

  • cli
  • api

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add martinffx/atelier --skill spec-finish --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Spec Finish?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Spec Finish
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/martinffx-spec-finish/badge)](https://www.skillsdirectory.com/skills/martinffx-spec-finish)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: spec-finish
description: >
  Post-implementation completion workflow. Use after spec-implement completes to validate,
  review, create stacked commits, and prepare for PR. Triggers when implementation is done,
  when the user says "finish", "done", "complete", or after implementation tasks are finished.
user-invocable: true
---

# Spec Finish

Post-implementation workflow: validate → review → stack commits → prepare PR.

## Prerequisites

Before starting, verify:
1. All implementation tasks complete
2. Working directory is clean (committed or staged)
3. Tests pass

If not complete → go back to spec-implement.

---

## Step 1: Validate

Run validation checks.

### Test Suite
```bash
npm test
# or
pytest
# or
cargo test
```

### Type Check
```bash
npm run typecheck
# or
python -m mypy
# or
cargo check
```

### Lint
```bash
npm run lint
# or
ruff check .
# or
cargo clippy
```

### Build
```bash
npm run build
# or
go build ./...
```

**If any fail:** Return to spec-implement to fix.

**If all pass:** Proceed.

---

## Step 2: Review

Use the Skill tool to invoke code-review skill for comprehensive code review.

### What to Review
- All changed files since feature branch
- Test coverage
- Documentation updates
- No debug code left

### If code-review finds issues
- Fix or note for follow-up
- Re-validate

---

## Step 3: Stack Commits

### Workflow
1. Review current commits: `git log --oneline`
2. Ensure commits are organized logically
3. Rebase if needed: `git rebase -i <base-branch>`
4. Ensure each commit is clean and functional

### Commit Guidelines
- Each commit should pass tests
- Use conventional commit format
- Meaningful commit messages

---

## Step 4: Update Documentation

Optional - use code-docs skill if needed.

### Check for Updates
- README changes needed?
- API documentation updated?
- Changelog updated?

### If documentation needed
- Load code-docs
- Update relevant docs
- Commit with docs

---

## Step 5: Prepare for PR

### Verify
- All tests passing
- All reviews complete
- Documentation updated
- Commits stacked properly

### Summary for Human

```
## Completion Summary

**Feature:** [name]
**Tests:** [passed/failed]
**Type Check:** [passed/failed]
**Lint:** [passed/failed]
**Commits:** [N commits in stack]
**Ready for PR:** [yes/no]
```

### Handoff

> "Implementation complete. [N] commits stacked. Ready for [submit/open PR]."

---

## Integration

This skill orchestrates other skills:

- Invokes code-review for quality check
- Invokes code-docs if documentation needs updates

---

## When NOT to Use

- If implementation still in progress → use spec-implement
- If tests failing → go back to spec-implement
- If review found blocking issues → go back to spec-implement

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.