ai-assisted-dev-toolkit

Manage GitLab merge requests, issues, and pipelines from the command line using the glab CLI. Use when the user asks about GitLab MRs, issues, pipelines, labels, milestones, or needs to manage project work items via the command line.

Manage Bitbucket pull requests, issues, and repositories from the command line using the bkt CLI. Use when the user asks about Bitbucket PRs, issues, repos, pipelines, or needs to manage project work items via the command line.

Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".

Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Build a compact mental model of recent project activity before any non-trivial task. Use proactively at the start of a session and before any investigation, planning, refactor, or multi-file change. Skip only for trivial fixes (typos, isolated docs, version bumps, mechanical refactors with a known target).

Interact with Jira from the command line using the official Atlassian CLI (acli) to create, search, view, edit, and transition work items, manage sprints and boards, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.

Manage GitHub Issues and Pull Request review threads from the command line using the gh CLI. Use when the user asks about GitHub issues, labels, milestones, PR review comments, resolving review threads, or needs to manage project work items via the command line.

Manage GitHub Issues and Pull Request review threads from the command line using the gh CLI. Use when the user asks about GitHub issues, labels, milestones, PR review comments, resolving review threads, or needs to manage project work items via the command line.

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.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when executing implementation plans with independent tasks in the current session

Use when you have a spec or requirements for a multi-step task, before touching code

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.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when executing implementation plans with independent tasks in the current session

Use when you have a spec or requirements for a multi-step task, before touching code

Use after coding sessions or before commits to analyze recently modified code for simplification opportunities. Two-phase process: generate suggestions, then spawn a Staff Engineer reviewer to validate before presenting recommendations. Do not make code changes — analyze and report only.

Use when dispatched to debug an issue — enforces systematic root cause investigation before any fix attempts. Complements the systematic-debugging skill with a structured dispatch template and reporting format.

Use for security-focused code audits on auth, payments, user data, API endpoints, or file uploads. Performs OWASP Top 10 checklist review. Dispatch as a fresh subagent with no shared context to avoid anchoring bias.

Comprehensive logging standards for applications including structured logging, log levels, message formatting, and observability guidelines

Strategy and tool resolution for interacting with issue trackers (Jira, GitHub Issues, Linear). Defines the MCP-first, CLI-fallback approach and provides the MCP tools reference. For CLI-specific commands, see the dedicated tracker skill (acli, gh-cli, or linear-cli).

Manage Linear issues from the command line using the linear CLI. This skill allows automating Linear issue management including creating, updating, querying, and commenting on issues.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Comprehensive logging standards for applications including structured logging, log levels, message formatting, and observability guidelines

Standards for creating and maintaining project documentation including README files, inline comments, API documentation, and architectural decision records

Standards for creating and maintaining project documentation including README files, inline comments, API documentation, and architectural decision records