github-commit
Create a well-formatted git commit following best practices
Best use case
github-commit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create a well-formatted git commit following best practices
Teams using github-commit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/github-commit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How github-commit Compares
| Feature / Agent | github-commit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create a well-formatted git commit following best practices
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Git Commit Skill When this skill is invoked, create a git commit following these steps: ## Instructions 1. **Check git status** to see what files are staged/unstaged 2. **Review the changes** using `git diff` (or `git diff --staged` if files are already staged) 3. **Verify no sensitive data** is being committed (secrets, private keys, API keys, tokens, credentials) 4. **Stage files if needed** with `git add` 5. **Create the commit** using `git commit -S` to sign the commit ## Commit Message Guidelines Follow these seven rules for great commit messages: 1. **Separate subject from body with a blank line** 2. **Limit the subject line to 50 characters** 3. **Capitalize the subject line** 4. **Do not end the subject line with a period** 5. **Use the imperative mood in the subject line** (e.g., "Add feature" not "Added feature") 6. **Wrap the body at 72 characters** 7. **Use the body to explain what and why vs. how** Additional guidelines: - **Style**: Casual and human, but professional - **Language**: Always in English - **Format**: - Short title describing the change - If more context is needed, add a blank line followed by a commit body with further clarifications ## Important Notes - Always use `-S` flag to sign commits with GPG - Be specific but concise - No need for issue numbers unless critical - Avoid generic messages like "fix bug" or "update code" - **Never commit sensitive data**: secrets, private keys, API keys, tokens, .env files, wallet private keys, seed phrases, mnemonics, keystore files, or any credentials ## References Based on: <https://chris.beams.io/git-commit>
Related Skills
github.com/n-r-w/ctxlog guidelines
Guidelines and examples for using the ctxlog logging package.
github-workflows
Initialize or update GitHub Actions workflows for Go projects with comprehensive CI/CD pipelines including linting, testing, coverage, snapshot builds, and releases. Use when setting up GitHub Actions automation for Go projects. Trigger with "setup github actions", "add github workflows", or "configure ci/cd".
github-search
Search GitHub for repos, code, and usage examples using gh CLI. Capabilities: repo discovery, code search, finding library usage patterns, issue/PR search. Actions: search, find, discover repos/code/examples. Keywords: gh, github, search repos, search code, find examples, how to use library, stars, language filter. Use when: finding repositories, searching code patterns, discovering how libraries are used, exploring open source.
github-repo-skill
Guide for creating new GitHub repos and best practice for existing GitHub repos, applicable to both code and non-code projects
github-repo-analysis
Analyze GitHub repositories to extract insights about commit frequency, outstanding contributors, release timeline, and project health metrics. Use when users request repository analysis, commit history investigation, contributor identification, release tracking, or development activity assessment for any GitHub project.
github-pr-review-comments
Comprehensive workflow for managing GitHub PR review comments using gh CLI and GraphQL API. Use when asked to address review comments, find unreplied comments, reply to review threads, or resolve/unresolve review conversations. Supports finding ALL comments across pagination boundaries, replying to threads, and resolving conversations.
github-navigator
GitHub operations via gh CLI. CRITICAL: Always use instead of WebFetch for ANY github.com URL. Use when user provides GitHub URL, says 'facebook/react', 'show README', 'list issues', 'check PR', 'clone repo', 'analyze this repo', 'understand the architecture', 'how is X structured', 'explore the codebase'. For deep analysis of external repos, clones locally.
github-issues
Manage GitHub issues - create, edit, close, comment, assign, and delegate to Copilot. Uses GitHub MCP.
github-issue-triage
Analyze GitHub issues for the Nx repository and provide assignment recommendations based on technology stack, team expertise, and priority classification rules.
github-issue-resolver
Strategically resolves GitHub Actions failures, failed pull requests, and Dependabot issues using the gh CLI with intelligent analysis and automated fixes.
github-issue-creator
Creates well-structured GitHub issues for the MCPSpy project using the gh CLI tool. Use when asked to create issues, report bugs, or document features. Follows conventional naming with feat/chore/fix prefixes and maintains appropriate detail levels.
github-copilot-agent-tips-and-tricks
Tips and Tricks for Working with GitHub Copilot Agent PRs