Commit
- 4 installs
- 21 repo stars
- Updated July 31, 2026
- jim60105/copilot-prompt
Review staged changes with git diff and create a conventional-commit-formatted git commit with a clear title and body in English.
About
Guides creating a git commit by first reviewing the full diff, then writing a conventional commit message with a descriptive body. A developer uses it to finalize changes with consistent, issue-linked commit messages.
- Conventional commit title plus bulleted body and optional issue resolution
- Emphasizes real newlines over literal \n in commit messages
Commit by the numbers
- 4 all-time installs (skills.sh)
- Ranked #480 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jim60105/copilot-prompt --skill commitAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 4 |
|---|---|
| repo stars | ★ 21 |
| Last updated | July 31, 2026 |
| Repository | jim60105/copilot-prompt ↗ |
What it does
Review staged changes with git diff and create a conventional-commit-formatted git commit with a clear title and body in English.
Files
Commit
Create git commits with conventional commit messages.
Steps
1. Run git --no-pager diff to review the full changes. 2. Analyze the changes thoroughly to understand what was modified. 3. Create a git commit with a clear, conventional commit message.
Commit Guidelines
Format
- Title: Use conventional commit format (
type: description) - Body: Include brief description linking to the issue
- Language: Always write commits in English
- Newline: Use real newlines in commit message, not
\n - Resolve Issues: If applicable, include "Resolves issue #X" in the body to link the commit to an issue. Skip this if there is no relevant issue.
IMPORTANT: Don't use \n that's not working, use real newlines!!! IMPORTANT: Don't use \n that's not working, use real newlines!!! IMPORTANT: Don't use \n that's not working, use real newlines!!!
Commit Command Template
git commit -m "chore: standardize linting, centralize guides, pin Python
- Introduce a root .flake8 config enforcing a 100-character line limit and ignoring specific style checks
- Remove inlined Python and Zsh guideline sections from copilot-instructions.md in favor of dedicated files
- Pin project Python version to 3.12 via a new .python-version file
- Rename docs/testing-guideline.md to docs/zsh-testing-guideline.md
- Refactor fetch_tags.py for consistent double-quoted strings, streamlined pattern definitions, logging calls, and URL assignment
Resolves issue #42"Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148