Back to Skills

complete

majiayu000
Updated Today
1 views
58
9
58
View on GitHub
Documentationword

About

The `complete` skill finalizes development tasks by validating implementation, updating documentation, and performing code reviews before automatically merging feature branches into develop. It's designed for use when all coding work is finished and ready for integration. The skill handles the full completion workflow including security audits, final commits, and branch cleanup.

Quick Install

Claude Code

Recommended
Plugin CommandRecommended
/plugin add https://github.com/majiayu000/claude-skill-registry
Git CloneAlternative
git clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/complete

Copy and paste this command in Claude Code to install this skill

Documentation

/complete

Complete a task with full validation, documentation updates, reviews, and automatic merge to develop.

Usage

/complete careerbrain 002         # Complete specific issue
/complete careerbrain             # Complete current/active issue

What It Does

  1. Validate PLAN completion and spec compliance
  2. Update all project documentation
  3. Create final commit with doc changes
  4. Run mandatory code review + security audit
  5. Merge to develop branch
  6. Clean up feature branch

GitFlow Pattern: feature/*develop (automatic) | developmain (requires PR)

Prerequisites

  • All implementation complete (code written)
  • Active issue with completed work
  • PLAN.md exists with phases mostly complete

Execution Flow

1. Check PLAN.md Completion

✓ All phases complete (5/5)
  or
✗ Incomplete phases:
  - [ ] 1.3 - Implement session refresh

2. Spec Compliance Validation

Acceptance Scenario Coverage:

  • Search tests matching each Given/When/Then scenario
  • Create missing tests if needed

Success Metrics Verification:

  • Check performance, coverage, accessibility

Out-of-Scope Enforcement:

  • Scan for code that violates out-of-scope items

Agent Constraints Check:

  • Verify no dependencies added (if constrained)
  • Check no files outside scope modified

3. Update Spec Status Markers

If the TASK has an implements: field, update inline status markers in the spec:

# Before (in spaces/[project]/docs/specs/*.md)
- 🚧 User registration with email/password

# After
- ✅ User registration with email/password

This provides public visibility into what's implemented.

4. Update All Documentation

Scan and validate ALL docs in spaces/[project]/docs/:

  • architecture-overview.md
  • data-model.md
  • api-overview.md
  • README.md

5. Update CHANGELOG

MANDATORY: Add entries under [Unreleased] section.

Categories:

  • ### Added - New features (TASKs)
  • ### Fixed - Bug fixes (BUGs)
  • ### Changed - Modifications
  • ### Security - Security updates

6. Final WORKLOG Entry

## YYYY-MM-DD HH:MM - COMPLETED

Issue ### complete and ready for merge.

Summary:
- [What was implemented]
- [What was deferred]

7. Update Status

Set issue frontmatter: status: complete

8. Create Final Commit

Stage and commit documentation changes.

9. Run Final Reviews

If not already done:

  1. Launch code-reviewer agent
  2. Launch security-auditor agent
  3. Block if CRITICAL issues

10. Merge to Develop

git checkout develop
git pull origin develop
git merge --no-ff feature/###-slug
git push origin develop
git branch -d feature/###-slug

11. Suggest Next Steps

Next actions:
1. Start next task: /implement project ### --full
2. View status: /project-status project
3. Merge to main (requires PR): gh pr create --base main --head develop

Documentation Checklist

Before merge, verify:

  1. PLAN.md - All phases checked off
  2. Linked SPEC - Updated to reflect what was built
  3. architecture-overview.md - Reflects changes
  4. ADRs - New decisions documented
  5. CHANGELOG.md - User-facing changes
  6. WORKLOG.md - Final summary
  7. README.md - Updated if API changed

Workflow

/issue → /plan → /implement → /commit → /complete
                                            ↓
                                    Update docs + CHANGELOG
                                            ↓
                                    Run reviews
                                            ↓
                                    Merge to develop

GitHub Repository

majiayu000/claude-skill-registry
Path: skills/complete

Related Skills

content-collections

Meta

This skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.

View skill

cloudflare-turnstile

Meta

This skill provides comprehensive guidance for implementing Cloudflare Turnstile as a CAPTCHA-alternative bot protection system. It covers integration for forms, login pages, API endpoints, and frameworks like React/Next.js/Hono, while handling invisible challenges that maintain user experience. Use it when migrating from reCAPTCHA, debugging error codes, or implementing token validation and E2E tests.

View skill

llamaindex

Meta

LlamaIndex is a data framework for building RAG-powered LLM applications, specializing in document ingestion, indexing, and querying. It provides key features like vector indices, query engines, and agents, and supports over 300 data connectors. Use it for document Q&A, chatbots, and knowledge retrieval when building data-centric applications.

View skill

canvas-design

Meta

The canvas-design skill generates original visual art in PNG and PDF formats for creating posters, designs, and other static artwork. It operates through a two-step process: first creating a design philosophy document, then visually expressing it on a canvas. The skill focuses on original compositions using form, color, and space while avoiding copyright infringement by never copying existing artists' work.

View skill