Menu
Audit commits for issues and CHANGELOG entries
| name | audit-commits |
| description | Audit commits for issues and CHANGELOG entries |
Compare HEAD against a tag, identify user-facing commits, ensure they have linked issues and CHANGELOG entries.
/audit-commits [tag]
No tag: suggest the most recent (git tag --sort=-creatordate | head -10).
git log --format="%h %s" <tag>..HEADgit show <sha> --stat and git show <sha>#<num> in message)[Unreleased] in CHANGELOG.mdUses Keep a Changelog format under [Unreleased].
| Change Type | Section |
|---|---|
| Feature | Added |
| Enhancement | Changed |
| Performance | Changed |
| Bugfix | Fixed |
| Deprecation | Deprecated |
| Removal | Removed |
- [Verb] [description] ([#issue](url))
Guidelines:
_Commit Graph_, _Home_ viewExample:
- Fixes an issue where the _Home_ view would not update when switching repositories ([#4717](https://github.com/gitkraken/vscode-gitlens/issues/4717))
Check [Unreleased] section for:
| 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.
Same workflow as /create-issue: duplicate detection, user confirmation, no auto-creation.
After creating: gh issue comment <num> --body "Closed by <commit_sha>"
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)"
Use for one-off / single-question inspection of the running GitLens extension — examining UI state, reading logs, checking feature flags, dispatching a command, or asking "what does the live DOM look like right now". Reference for `vscode-inspector` MCP primitives. For iterative debug-and-fix loops on UI bugs (sweep → fix → re-verify), use `/live-exercise` instead.
Add new icons to the GitLens GL Icons font
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees following GitLens conventions
Use whenever any UI-bearing work touches a running instance — building or fixing a feature, ship-gating, auditing, OR debugging visible bugs (flaky behavior, intermittent rendering, "sometimes does X" reports, hover/focus/animation glitches, layout overflow). Keep a running instance in the loop and exercise it as a user would. Adaptive depth from tactical fix-loop to ship-gate audit. Not for pure-logic diff review.
Investigate bugs — single-issue deep root cause analysis or batch parallel investigation from a report or issue list
Use when you want to iterate on a feature interactively with the user watching a running instance — pair-programming rhythm for UI-heavy work, redesigns, copy tightening, layout exploration, or any "let me just show you what I want" session. Not for systematic audit (/live-exercise) or perf-tuning (/live-perf).