skills.rest
jmduea
jmdueaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

completion-finisher

Validates README, specification, changelog completeness and generates commit plan suggestions after task completion.

Updated Feb 12, 2026
Search Tags:#git#documentation#code-completion#commit-grouping#docs-freshness
One-click install
npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill completion-finisher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: completion-finisher
Source: https://github.com/jmduea/emotiv-cortex-rs/tree/main/.github/skills/completion-finisher
Command: npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill completion-finisher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures that documentation is up‑to‑date and commit histories are logically grouped when a coding task is finished, preventing missing changelog entries and ambiguous commits.

Core Features & Use Cases

  • Docs freshness check: Verifies that README, specifications, and changelog reflect recent code changes.
  • Commit grouping validation: Confirms that commits are scoped, non‑overlapping, and clearly described.
  • Output suggestions: Provides pass/fail results for docs checks and suggests structured commit messages.
  • Use Case: After completing a feature branch, run this skill to confirm documentation integrity and receive a clean commit plan before merging.

Quick Start

Run the completion-finisher skill after finishing a coding task to validate docs and get a structured commit plan.

Frequently Asked Questions about completion-finisher

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

FAQPage Schema
How do I verify README and changelog freshness before merging a feature branch?▼

Docs freshness verification checks that README, specifications, and changelog entries reflect recent code changes before merging a feature branch, generating pass or fail results for documentation completeness.

What is the best way to group git commits into coherent, scoped groups?▼

Commit grouping validation confirms that git commits are scoped, non-overlapping, and clearly described, providing structured commit message suggestions to ensure a clean and audit-friendly project history.

How do I ensure code changes are accompanied by required documentation updates?▼

Documentation updates are enforced at task completion by applying checks for docs presence and completeness, verifying that code changes are accompanied by up-to-date README and specification entries.

Can I use this to generate a structured commit plan after finishing a coding task?▼

You can generate a structured commit plan after finishing a coding task by validating documentation integrity and receiving structured commit message suggestions that meet clear audit-friendly standards.

Does this check for missing changelog entries when a coding task is finished?▼

The check for missing changelog entries prevents incomplete documentation when a coding task is finished, verifying that changelog entries and specifications accurately reflect the completed code changes.

When do I need to validate commit histories and documentation freshness?▼

Validation of commit histories and documentation freshness is needed after completing a feature branch, ensuring documentation integrity and coherent commit grouping before merging into the main workflow.

Related Skills

Explore More Software Engineering Skills→
xtrm-devxtrm-dev
4

documenting

Detect documentation drift and update memories, changelogs, and README files.

Official
Advanced
rajivpantrajivpant
15

synthesis-preflight

Assess git branch readiness with six checks and a go/no-go verdict.

Community
Advanced
Kushal9889Kushal9889

husky

Sets up Husky git hooks to automate code quality checks and testing before commits.

Community
Intermediate
SfzmangoSfzmango
1

release-notes

Compile release notes from git commit ranges and merged pull requests.

Community
Advanced