finalize-feature

Analyzes repository changes and creates a finalized commit without pushing.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/voidreader/band-of-mercenaries --skill finalize-feature-voidreader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finalize-feature
Source: https://github.com/voidreader/band-of-mercenaries/tree/main/.agents/skills/finalize-feature
Command: npx skills add https://github.com/voidreader/band-of-mercenaries --skill finalize-feature-voidreader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of wrapping up completed feature work by analyzing changes, updating the right project documents, and creating a commit with the correct scope and message format.

Core Features & Use Cases

  • Change Analysis: Reviews the current git status and diff to infer what feature or fix was completed.
  • Commit Preparation: Determines the proper commit scope and generates a multi-line commit message that follows the repository’s conventions.
  • Documentation Sync: Updates CLAUDE.md when required, creates changelog fragments, and archives spec-related documents when the workflow calls for it.
  • Use Case: A developer finishes a gameplay feature and wants the repository cleaned up, documented, and committed without accidentally pushing changes.

Quick Start

Ask the assistant to finalize the current feature by reviewing the diff, updating the required documentation, creating the changelog fragment, and committing the changes without pushing.

Frequently Asked Questions about finalize-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I finalize a git feature branch with proper changelog and commit message formatting?

To finalize a git feature, the workflow analyzes staged files and diffs to detect scope, updates changelog fragments documentation, and creates a heredoc-formatted multi-line commit message following repository conventions.

What is the best way to update documentation and create a commit after finishing a feature?

The best way to update documentation after finishing a feature is to synchronize CLAUDE.md, generate changelog fragments, archive spec documents conditionally, and prepare a scoped commit message automatically from the diff review.

Can I use this feature finalization workflow without accidentally pushing my changes to the remote?

Yes, this feature finalization workflow enforces a hard stop before any git push, ensuring your local commit is created with documentation updates without sending changes to the remote repository.

Does this git commit workflow handle changelog fragment updates and spec document archiving automatically?

Yes, this git commit workflow handles changelog fragment creation, CLAUDE.md synchronization, and conditional spec document archiving automatically by inspecting the current repository changes and diff.

What limitations should I expect when finalizing a feature commit with staged-file inspection?

A key limitation of finalizing a feature commit here is that it requires staged files for inspection and will not execute a git push, meaning unstaged changes are excluded and remote delivery remains manual.

Do I need to manually write commit messages or does this workflow generate them from the diff?

You do not need to manually write commit messages, as this workflow generates heredoc-formatted multi-line commit messages by analyzing your staged-file diffs and determining the proper scope based on repository conventions.