A collection of AI agent skills

Symlink this repo into your Claude Code skills directory:

mkdir -p ~/.claude/skills
ln -s /path/to/ai-skills/* ~/.claude/skills/

This makes all skills available globally across projects.

Manage Jira projects using the ankitpokhrel/jira-cli command line tool. Covers creating, listing, searching, viewing, editing, transitioning, assigning, and commenting on issues, as well as managing epics and boards. Ensures commands use non-interactive flags (--plain, --no-input) so they work reliably in an agent context, and includes a detailed reference for JQL queries, data extraction with jq, and common workflow patterns.

Start working on a Jira ticket with a single command. Orchestrates the full “begin work” workflow:

/jira-work JAVA-6111
/jira-work JAVA-6111 - focus on backpressure handling

What it does:

1. Looks up the local repo path for the project from jira-work/config.yml (prompts you on first use)
2. Checks for uncommitted work — refuses to proceed if the workspace is dirty
3. Updates main from upstream (or origin)
4. Creates a feature branch named after the ticket (e.g., JAVA-6111)
5. Fetches the full Jira ticket and comments using the jira-cli skill
6. Delegates to superpowers' writing-plans to create a detailed implementation plan with bite-sized TDD tasks
7. Offers execution choice (subagent-driven or inline)

Subcommands (after a plan exists):

/jira-work implement     # execute the plan using superpowers
/jira-work code-review   # run /multi-review on changes against main
/jira-work commit        # commit changes and push branch to origin

Requires:

• superpowers plugin installed (/plugin install superpowers@claude-plugins-official)
• Local jira-cli skill for all Jira commands
• ankitpokhrel/jira-cli installed and configured

Portable multi-agent code review orchestrator. Captures a diff, dispatches parallel review agents, and synthesizes their findings into a single consolidated review.

/multi-review main              # diff current branch against main
/multi-review #123              # review PR 123
/multi-review release/1.0       # diff against a specific branch
/multi-review                   # auto-detects (open PR or primary branch)

Add extra focus with -:

/multi-review main - ensure concurrency safety
/multi-review #123 - check binary compat

How it works:

1. Captures the diff (auto-detects PR vs branch, resolves remotes)
2. Dispatches parallel review agents:
   • Domain agent (reads project AGENTS.md/CLAUDE.md for rules)
   • General quality reviewer (correctness, architecture, tests)
   • Code quality reviewer (reuse, efficiency, patterns)
   • PR comment checker (if PR has existing review comments)
3. Synthesizes all findings into a single consolidated review

Carries no domain knowledge — portable across any project with AGENTS.md.

Requires superpowers plugin installed.

Stress-test your understanding of a code change by answering questions about it. Works for both PR authors (self-check before submitting) and reviewers (verify you didn't rubber-stamp).

/grill-review main              # grill on diff against main
/grill-review #123              # grill on PR 123
/grill-review src/Handler.java  # grill on a specific file
/grill-review                   # auto-detects (open PR or primary branch)

How it works:

1. Captures the diff or reads files (same detection logic as multi-review)
2. Builds an internal risk map of the change (complexity, impact, novelty, coverage)
3. Asks pointed questions one at a time across four categories: Intent & Motivation → Mechanics & Correctness → Impact & Integration → Testing
4. Verifies your answers against the actual code
5. Concludes with a confidence verdict per category

Thin wrapper around multi-review for backward compatibility. Accepts the same arguments and delegates directly.

Look up and summarize MongoDB driver specifications from the official mongodb/specifications repository.

/specifications crud                  # summarize the CRUD spec
/specifications backpressure          # fuzzy matches to client-backpressure
/specifications                       # list all specs grouped by category

What it does:

1. Clones (or updates) the specifications repo locally
2. Fuzzy-matches partial spec names to the correct specification
3. Checks a local summary cache keyed by the spec file's git commit hash — serves cached summaries instantly when the spec hasn't changed
4. Reads the full spec and produces a structured summary (Purpose, Key Concepts, Driver Requirements, API Surface, Error Handling, Testing Notes, Related Specs, Changelog Highlights)
5. Caches the summary for future lookups