commit-closer

Generate commit messages and PR descriptions from git diffs and commit ranges.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nico0695/ai-tools --skill commit-closer-nico0695
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-closer
Source: https://github.com/nico0695/ai-tools/tree/main/skills/generic-skills/commit-closer
Command: npx skills add https://github.com/nico0695/ai-tools --skill commit-closer-nico0695

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear commit messages and thorough PR descriptions is repetitive and often skipped under time pressure, leaving teams with vague history and risky, under-reviewed changes. This Skill turns staged or committed git changes into structured, review-ready documentation. ## Core Features & Use Cases - Commit Message Drafting: Produces six Conventional Commits options (three full messages with body and footers, three one-liners) based on the actual diff and your stated intent. - PR Description Generation: Builds a complete PR description with change summary, per-file modification table, project impact analysis, and an actionable manual testing checklist. - Multi-Commit Analysis: Optionally incorporates earlier commits from the same PR by hash range, then regenerates a unified description and impact assessment. - Use Case: After finishing a feature touching the reminders controller and services, run the Skill to get six commit message candidates, a PR description listing every modified file, and a checklist of specific scenarios to verify before merging. ## Quick Start Ask the assistant to use the commit-closer skill to draft a commit message and PR description for your current staged changes.

Frequently Asked Questions about commit-closer

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

FAQPage Schema
How do I generate a commit message from staged git changes?▼

Stage your changes with git add, then invoke the Skill. It runs git status, git diff, and git log to inspect the changes, asks what you changed and why, then produces six Conventional Commits options to choose from.

How to write a PR description from multiple commits?▼

The Skill offers an optional step to include earlier commits. Specify a commit count or hash range, confirm the listed commits, and it runs git show on each to merge their changes into one unified PR description and impact analysis.

Does it follow the Conventional Commits format?▼

Yes. It generates type-prefixed subjects like feat(scope): summary with imperative mood, 72-character limits, optional bodies explaining what and why, and footers such as BREAKING CHANGE or Closes #X.

Can it analyze the impact of my code changes?▼

Yes. It reads every modified file, cross-references related modules, and flags risks affecting controllers, event handlers, singletons, or global state in a dedicated project impact section of the PR description.

What are the limitations of automated commit message generation?▼

The Skill requires your answers about what changed and why before proceeding, since diffs alone cannot reveal intent. It also warns that Husky pre-commit hooks running lint and tests may abort the commit if they fail.