audit-commits
Audit commits for issues and CHANGELOG entries
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- audit-commits
- description
- Audit commits for issues and CHANGELOG entries
03 SKILL.md 正文
/audit-commits - Audit Commits
Compare HEAD against a tag, identify user-facing commits, ensure they have linked issues and CHANGELOG entries.
Usage
/audit-commits [tag]
No tag: suggest the most recent (git tag --sort=-creatordate | head -10).
Workflow
- Fetch commits:
git log --format="%h %s" <tag>..HEAD - Analyze each (oldest first):
- Get diff:
git show <sha> --statandgit show <sha> - Classify: bugfix / feature / refactor / docs / tests / chore
- Assess impact: High / Medium / Low / None
- Check for linked issue (
#<num>in message)
- Get diff:
- Group related commits (e.g., feature + immediate follow-up fix)
- Check each user-facing commit against
[Unreleased]in CHANGELOG.md - Present summary, confirm before creating issues or editing CHANGELOG
Impact Assessment
| Impact | Criteria |
|---|---|
| High | New feature, breaking change, significant bugfix |
| Medium | Enhancement, minor bugfix, performance improvement |
| Low | Edge case fix, minor polish |
| None | Refactor, internal cleanup, tests, docs-only |
User-facing (High/Medium/Low) require issue + CHANGELOG. None = skip.
Issue Creation
Same workflow as /create-issue: duplicate detection, user confirmation, no auto-creation.
After creating: gh issue comment <num> --body "Closed by <commit_sha>"
Progress Display
Auditing commits: <tag>..HEAD
Summary:
- Total commits: 25
- User-facing: 12 (missing issue: 3, missing CHANGELOG: 5)
- Not user-facing: 13 (skipped)
Then ask: "Process these commits? (create issues / update CHANGELOG / both / skip)"
Safety
- NEVER include code snippets or implementation details in issues
- NEVER create labels without user confirmation
- NEVER auto-create issues or edit CHANGELOG without user confirmation
04 同仓库更多 Skills
winui-app
Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.
vercel-deploy
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
security-best-practices
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
playwright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
openai-docs
Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; prioritize OpenAI docs MCP tools, use bundled references only as helper context, and restrict any fallback browsing to official OpenAI domains.
netlify-deploy
Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.