all publishers

gitkraken

@gitkraken source repo

32 published skills

  1. ▌
    Openspec Propose · gitkraken
    Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
    10k repo stars
  2. ▌
    Gitbench Analyze Models · gitkraken bundle
    Analyze GitBench model evaluations through its public read-only API. Use when comparing model quality, cost, API time, or token efficiency on Git tasks; finding exact evaluated model identities; inspecting benchmark or fixture outcomes; explaining model successes or failures with bounded evidence; or making a resource-aware model recommendation from GitBench results.
    10k repo stars
  3. ▌
    Openspec Apply Change · gitkraken
    Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
    10k repo stars
  4. ▌
    Openspec Explore · gitkraken
    Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
    10k repo stars
  5. ▌
    Commit · gitkraken
    Create well-formatted git commits following GitLens conventions
    10k repo stars
  6. ▌
    Review · gitkraken
    Code review against GitLens standards with optional impact completeness audit
    10k repo stars
  7. ▌
    Triage · gitkraken
    Triage GitHub issues using an evidence pack — evaluates issues and produces a structured report with verdicts, confidence levels, and recommended actions
    10k repo stars
  8. ▌
    Add Icon · gitkraken
    Add new icons to the GitLens GL Icons font
    10k repo stars
  9. ▌
    Add Test · gitkraken
    Generate unit or E2E test files for existing code
    10k repo stars
  10. ▌
    Worktree · gitkraken
    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees following GitLens conventions
    10k repo stars
  11. ▌
    Dev Scope · gitkraken
    Scope a unit of work into a goals document — defines what and why, not how. Bridge between triage output and dev planning. Produces .work/dev/{identifier}/goals.md for /deep-planning to consume.
    10k repo stars
  12. ▌
    Live Pair · gitkraken
    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).
    10k repo stars
  13. ▌
    Live Perf · gitkraken
    Use when you want to measure and improve the performance of a feature in the running extension, hunt regressions, or perf-tune before shipping. Standalone for perf-tuning an existing feature; also invoked by /live-exercise Phase 7. Not for static code review without measurement.
    10k repo stars
  14. ▌
    UX Review · gitkraken
    Use when reviewing a change set for user experience quality — traces user flows instead of code paths, validates that the implementation delivers the right experience against the goals doc's UX spec
    10k repo stars
  15. ▌
    A11Y Audit · gitkraken bundle
    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.
    10k repo stars
  16. ▌
    Modern CSS · gitkraken bundle
    Use when touching any CSS — new files, edits, audits, refactors, `<style>` blocks, CSS-in-JS, Tailwind config, design-token files, or reviewing CSS a teammate wrote. Applies to vanilla CSS, shadow DOM internals, web-component consumers, VS Code webviews, and framework-scoped styles. Skip only for files with no styles at all (e.g. `.py`/`.go`/`.rs` without embedded CSS).
    10k repo stars
  17. ▌
    Prioritize · gitkraken
    Prioritize triaged/investigated issues — recommends shortlist, backlog, won't fix, or community contribution with priority signals and draft communications
    10k repo stars
  18. ▌
    Add Command · gitkraken
    Create new VS Code commands with all required boilerplate
    10k repo stars
  19. ▌
    Add Webview · gitkraken
    Create new webviews with RPC services, Lit app, and registration
    10k repo stars
  20. ▌
    Deep Review · gitkraken
    Use to gate a change set before merge — delegates bug-hunting to the built-in code-review skill, then layers goals.md alignment, cross-platform/consumer completeness, and validation-gap analysis into a merge verdict. For standards/checklist compliance use /review.
    10k repo stars
  21. ▌
    Investigate · gitkraken
    Investigate bugs — single-issue deep root cause analysis or batch parallel investigation from a report or issue list
    10k repo stars
  22. ▌
    Create Issue · gitkraken
    Create GitHub issues from uncommitted changes or commits
    10k repo stars
  23. ▌
    Live Inspect · gitkraken
    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.
    10k repo stars
  24. ▌
    Audit Commits · gitkraken
    Audit commits for issues and CHANGELOG entries
    10k repo stars
  25. ▌
    Deep Planning · gitkraken
    Use when formulating the best technical approach for a task — before writing implementation plans or code. Triggers on architecture decisions, complex features, refactors, or when the user asks how to approach something. Investigates current codebase, questions existing patterns, researches alternatives, and presents approaches with trade-offs.
    10k repo stars
  26. ▌
    Live Exercise · gitkraken
    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.
    10k repo stars
  27. ▌
    Update Issues · gitkraken
    Update GitHub issues from triage, investigation, or prioritization reports — adds labels, posts comments, sets milestones, and closes issues with safety checks
    10k repo stars
  28. ▌
    A11Y Remediate · gitkraken bundle
    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.
    10k repo stars
  29. ▌
    Challenge Plan · gitkraken
    Use when reviewing or stress-testing a proposed technical approach, implementation plan, or architecture decision. Triggers when asked to review a plan, play devil's advocate, poke holes, or validate an approach before implementation begins.
    10k repo stars
  30. ▌
    A11Y Flow Audit · gitkraken bundle
    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.
    10k repo stars
  31. ▌
    Changelog Story · gitkraken
    Reorganize the CHANGELOG's [Unreleased] section into a release "story" — pillar features become umbrella entries with sub-bullets, wording gets tightened to expert release-notes quality, and intra-release-only fixes get pruned by verifying against the last stable tag. Use whenever the user asks to make the changelog tell a story, reorganize/consolidate/group the unreleased section, prep the CHANGELOG for a release, or complains the unreleased section is too long, too detailed, or disorganized — even if they just say "clean up the changelog". Not for adding individual entries (that's /audit-commits or /commit).
    10k repo stars
  32. ▌
    Consolidate Commits · gitkraken
    Consolidate a feature branch's commits into the minimum number of valuable commits with no add-then-undo churn, verifying the final tree is byte-identical. Use whenever the user asks to clean up, consolidate, squash, restructure, or curate a branch's commits, wants "reviewable commits" before landing or opening a PR, or complains that a branch's history is messy or has churn — even if they don't say "squash".
    10k repo stars