pi-gauntlet

In the author's own words, from each skill's SKILL.md.

• brainstorming

  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.

  skills/brainstorming/SKILL.md on GitHub (opens in a new tab)

• chase-bug

  Use when a human hands you a bug report to triage - a Slack paste, tracker ticket, GitHub issue, or described symptom - and the goal is an evidenced verdict (real bug, not-a-bug, cannot reproduce, already fixed or reported); triage itself never fixes - a real-bug verdict may hand off to a bounded hotfix after the menu.

  skills/chase-bug/SKILL.md on GitHub (opens in a new tab)

• check-delivery

  Use when a merged issue needs delivery proof before its tracker status advances - explicit-only post-merge detective control (/skill:check-delivery <ticket-ref>) that verifies default-branch landing, delivery target, and per-AC evidence, stopping loudly with zero writes on any failure.

  skills/check-delivery/SKILL.md on GitHub (opens in a new tab)

• dispatching-parallel-agents

  Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies, when fanning out review-finding fixes in parallel, or when checking a reviewer's Parallel-safe: line before doing so

  skills/dispatching-parallel-agents/SKILL.md on GitHub (opens in a new tab)

• finishing-a-development-branch

  Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

  skills/finishing-a-development-branch/SKILL.md on GitHub (opens in a new tab)

• forge-skill

  Use when creating or editing a SKILL.md, a skill's reference file, an agent persona, a prompt template, or a slash command in pi or Claude Code - including one-line edits - or when such a file exceeds 500 lines, gains if/else branching, or drifts from imperative voice; the authoring skill for repos that follow gauntlet's conventions.

  skills/forge-skill/SKILL.md on GitHub (opens in a new tab)

• gatekeep-pr

  Use when gating a pull request before it merges - whether you authored it or are reviewing someone else's work. Consent-gated - verification is read-only, every externally visible mutation (fix commits, pushes, reviews, merges) waits for explicit selection.

  skills/gatekeep-pr/SKILL.md on GitHub (opens in a new tab)

• gauntlet-handoff

  Human-only producer of a gauntlet handoff brief - invokes pi-cohort's `handoff` skill, then appends the gauntlet process-state section (phase/plan tracker status) to the brief it wrote, per the shared brief contract. Run at the end of a session whose flow a fresh session will continue with /skill:gauntlet-resume.

  skills/gauntlet-handoff/SKILL.md on GitHub (opens in a new tab)

• gauntlet-performance

  Use when a human asks how gauntlet runs perform across the recorded telemetry - explicit invocation only (/skill:gauntlet-performance [--dir <path>]... [--since <version>]).

  skills/gauntlet-performance/SKILL.md on GitHub (opens in a new tab)

• gauntlet-resume

  Use when a human wants to continue an interrupted gauntlet flow in a fresh session - from a gauntlet-handoff brief (file, pasted, or picked from the default handoff directory), from a bare worktree that already holds a spec, or from a spec tracked on main (creates or reuses its worktree via `/skill:using-git-worktrees`). Human-only; the sole resume entry point. Restores phase/plan tracker state t…

  skills/gauntlet-resume/SKILL.md on GitHub (opens in a new tab)

• linear

  Use when reading, searching, commenting on, editing, or managing Linear tickets via the `linearis` CLI - ticket IDs like ABC-123, "check ticket ABC-99", "move ABC-12 to done", or when a tracker-facing skill routes Linear mechanics here. Authoring a NEW ticket (structure, acceptance criteria) belongs to /skill:shape-ticket, which calls this skill's create mechanic.

  skills/linear/SKILL.md on GitHub (opens in a new tab)

• receiving-code-review

  Use when receiving code review feedback from a human or external reviewer (GitHub review, human partner), before implementing suggestions, especially when feedback is unclear or technically questionable - verify, push back with evidence, never perform agreement; the subagent-driven-development review-fix loop is out of scope

  skills/receiving-code-review/SKILL.md on GitHub (opens in a new tab)

• requesting-code-review

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

  skills/requesting-code-review/SKILL.md on GitHub (opens in a new tab)

• roasting-the-spec

  Use after writing a spec, when a spec council is configured (the resolved piGauntlet.specCouncil council, via the gauntlet_setting tool, repo settings over the preset). Auto-dispatched by /skill:brainstorming as the critique pass when members is non-empty (no longer offered). N members on different models critique in parallel, a neutral chair consolidates and adjudicates, the parent applies its o…

  skills/roasting-the-spec/SKILL.md on GitHub (opens in a new tab)

• shape-ticket

  Use when creating a new tracker issue from a request, repairing or cleaning up an existing tracker issue, or converting a vague ask into an actionable ticket with real acceptance criteria. Also explicit invocation via /skill:shape-ticket.

  skills/shape-ticket/SKILL.md on GitHub (opens in a new tab)

• subagent-driven-development

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

  skills/subagent-driven-development/SKILL.md on GitHub (opens in a new tab)

• test-driven-development

  Use when implementing any feature or bugfix, before writing implementation code

  skills/test-driven-development/SKILL.md on GitHub (opens in a new tab)

• using-git-worktrees

  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

  skills/using-git-worktrees/SKILL.md on GitHub (opens in a new tab)

• verification-before-completion

  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

  skills/verification-before-completion/SKILL.md on GitHub (opens in a new tab)

• writing-plans

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

  skills/writing-plans/SKILL.md on GitHub (opens in a new tab)

• release

  Use when asked to release, publish, bump the version, or cut a tag for jjuraszek/pi-gauntlet.

  .agents/skills/release/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• reaby morluto Reverse engineer anything with agents, from app behavior down to native binaries. 412k stars · 5 skills
• superpowersby obra An agentic skills framework & software development methodology that works. 309k stars · 15 skills
• skillsby mattpocock Skills for Real Engineers. Straight from my .agents directory. 307k stars · 30 skills
• ECCby affaan-m The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Cod… 293k stars · 30 skills
• andrej-karpathy-skillsby multica-ai A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls. 227k stars · 1 skill
• skillsby anthropics Public repository for Agent Skills 185k stars · 19 skills