Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/tuanductran/hr-skills/github-awesome-copilot-git-commitnpx skills add tuanductran/hr-skills --skill github-awesome-copilot-git-commitgit clone --depth 1 https://github.com/tuanductran/hr-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tuanductran/hr-skills/github-awesome-copilot-git-commit)<a href="https://agentmods.dev/skills/tuanductran/hr-skills/github-awesome-copilot-git-commit"><img src="https://agentmods.dev/badge/skills/tuanductran/hr-skills/github-awesome-copilot-git-commit.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00045 | $0.01242 |
| Opus 5 | $0.00023 | $0.00621 |
| Sonnet 5 | $0.00009 | $0.00248 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
github-awesome-copilot-git-commit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Awesome Copilot Git Commit
Supported tasks
Commit generation
- Generate Conventional Commit messages from Git diffs
- Analyze the current working tree using
git diff - Generate commit messages from staged changes using
git diff --cached - Infer the best commit type from the actual intent of the change
- Recommend an appropriate scope when it improves clarity
- Write concise subjects in the imperative mood (≤72 characters)
- Generate optional commit bodies explaining what changed and why
- Generate footers for issue references and breaking changes
Commit review
- Review uncommitted Git changes before creating commits
- Detect unrelated changes mixed in the same diff
- Recommend splitting large changes into multiple atomic commits
- Explain why commits should be separated
- Generate one Conventional Commit for each logical change
- Ignore whitespace-only changes unless intentional
Interactive Git workflow
- Review
git diffbefore staging - Review
git diff --cachedbefore committing - Suggest files that should be committed together
- Recommend staging strategies using
git add -p - Help create clean Git history with atomic commits
Validation
- Validate commit messages against Conventional Commits 1.0.0
- Detect incorrect types, scopes, formatting, or grammar
- Suggest improved commit messages
- Validate subject length
- Detect non-imperative subjects
- Detect unnecessary scopes
Pull requests
- Generate PR titles from commits
- Generate concise PR descriptions
- Summarize major changes
- Highlight breaking changes
- List testing notes
- Draft reviewer checklists
Releases
- Generate changelog entries
- Group commits into release categories
- Draft release notes
- Detect breaking changes
- Generate migration notes
- Summarize notable improvements
Key prompts
Generate commit from current changes
- "Analyze the current Git working tree by running
git diffand generate the best Conventional Commit." - "Review my current changes and recommend whether they should be split into multiple commits."
- "Generate a Conventional Commit from the current unstaged changes."
- "Generate a Conventional Commit from
git diff --cached."
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 177 lines · 45 tokens per session scan A 855aa4fe1345
github-awesome-copilot-git-commit is a skill published in the GitHub repository tuanductran/hr-skills (54 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 1,242 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…