Menu
Create GitHub issues from uncommitted changes or commits
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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). Adaptive depth from tactical fix-loop to ship-gate audit. Not for pure-logic diff review.
Use to audit a component, file, or directory for WCAG 2.1 AA accessibility compliance. Detects ARIA anti-patterns, missing semantics, keyboard gaps, and color-only information. Safety-first — refuses to emit fixes that would create a new accessibility bug. Scope is always explicit; do not use for page-level flow or cross-program planning.
Use to audit a page, view, or composed flow for WCAG 2.1 AA compliance at the composition level - landmarks, heading hierarchy, tab order across components, focus handoff on modal open/close, live-region conflicts. Scope is page/view, NOT component internals. Safety-first - refuses to emit fixes that would create a new a11y bug. For single-component audits use /a11y-audit; for cross-program planning use /a11y-remediate.
Use to produce a leader-facing remediation proposal from one or more /a11y-audit outputs plus team and product context. Translates audit findings into sprint plans, staffing asks, customer-facing language, compliance rollups, and critical-path analysis. Refuses to fabricate numbers, owners, or commitments beyond the inputs it has.
Add new icons to the GitLens GL Icons font
| name | create-issue |
| description | Create GitHub issues from uncommitted changes or commits |
Analyze changes and create GitHub issues with CHANGELOG entries.
/create-issue [source]
source: "uncommitted", a commit SHA, or a range like "abc123..def456"git diff), single commit (git show <sha>), or range (git diff <range>)gh search issues --repo gitkraken/vscode-gitlens "<keywords>"[Unreleased], confirm with user firstScore matches 0-1:
Thresholds: >= 0.7 likely duplicate, 0.45-0.69 possibly related, < 0.45 ignore.
| Section | Content |
|---|---|
| Summary | One-line description |
| Impact | Who/what benefits |
| Validation | Steps to verify |
| Risk | Potential regressions |
gh issue create --title "<title>" --body "<body>" --assignee @me --label "<labels>"
gh label list --limit 100Format per /audit-commits CHANGELOG conventions. Map: Feature→Added, Enhancement→Changed, Bugfix→Fixed, Removal→Removed.