Skip to main content
GitHub repository

ai-tools

ai-tools contains 18 collected skills from bang9, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
18
Stars
10
updated
2026-03-27
Forks
1
Occupation coverage
5 occupation categories · 100% classified
repository explorer

Skills in this repository

whip-pr-followup
software-developers

Triage unresolved PR review threads via webform and dispatch fixes through whip-start. Use after receiving review feedback on your own PR.

2026-03-27
whip-pr-followup
software-developers

Triage unresolved PR review threads via webform and dispatch fixes through whip-start. Use after receiving review feedback on your own PR.

2026-03-27
whip-debug
software-developers

Systematic debugging loop — reproduce, analyze root cause, fix, then challenge with a fresh verification pass to distinguish fundamental fixes from workarounds. Use when debugging issues or when unexpected behavior needs a methodical approach.

2026-03-24
whip-simulate
software-quality-assurance-analysts-and-testers

Run multi-agent simulations to measure output consistency. Use when you want to A/B test, validate behavioral equivalence, or stress-test non-deterministic behavior at scale.

2026-03-24
whip-debug
software-developers

Systematic debugging loop — reproduce, analyze root cause, fix, then challenge with a fresh verification pass to distinguish fundamental fixes from workarounds. Use when debugging issues or when unexpected behavior needs a methodical approach.

2026-03-24
whip-lgtm
software-quality-assurance-analysts-and-testers

Iterative review-fix loop — dispatch a fresh codex reviewer each round, apply fixes, repeat until LGTM. Use when you want rigorous code quality validation before merge.

2026-03-24
whip-simulate
software-developers

Run multi-agent simulations to measure consistency of non-deterministic behavior. Use when the user wants to A/B test, validate behavioral equivalence, or stress-test outputs at scale.

2026-03-24
whip-lgtm
software-quality-assurance-analysts-and-testers

Iterative review-fix loop — dispatch a fresh codex reviewer each round, apply fixes, repeat until LGTM. Use when you want rigorous code quality validation before merge.

2026-03-23
whip-start
computer-occupations-all-other

Spawn whip agent sessions to handle tasks. Dispatch a single agent or assemble a small team with explicit backend, scope, and ownership.

2026-03-20
whip-start
computer-occupations-all-other

Spawn whip agent sessions to handle tasks. Dispatch a single agent or assemble a small team with explicit backend, scope, and ownership.

2026-03-20
rewind-analyze
software-developers

Analyze a session transcript with AI and generate structured insights (prompt quality, strategy critique, key decisions, takeaways) for the rewind viewer.

2026-03-20
rewind-analyze
software-quality-assurance-analysts-and-testers

Analyze a session transcript with AI and generate structured insights (prompt quality, strategy critique, key decisions, takeaways) for the rewind viewer.

2026-03-20
whip-docs
technical-writers

Write or update documentation with code-verified accuracy. Use when creating, reviewing, or updating docs, READMEs, guides, or API references.

2026-03-20
whip-plan
computer-and-information-systems-managers-113021

Turn a multi-agent request into a concrete 6-phase whip plan, get user approval, save it under ~/.whip/plans, then hand off to $whip-start for execution.

2026-03-20
whip-docs
technical-writers

Write or update documentation with code-verified accuracy. Use when creating, reviewing, or updating docs, READMEs, guides, or API references.

2026-03-20
whip-plan
computer-and-information-systems-managers-113021

Analyze work, design a stacked task plan, and get user approval before execution. Use when starting a multi-task project that needs planning.

2026-03-20
whip-lesson-learn
software-developers

Create a real-world whip case-study or lessons-learned markdown file under .whip/lesson-learn/<file-name>.md. Use when the user wants to capture an actual whip run, prompts, decisions, IRC coordination, outcomes, or lessons learned. Prefer the explicitly requested language; otherwise use the user's conversation language.

2026-03-09
whip-lesson-learn
technical-writers

Create a real-world whip case-study or lessons-learned markdown file under .whip/lesson-learn/<file-name>.md. Use when the user wants to capture an actual whip run, prompts, decisions, IRC coordination, outcomes, or lessons learned.

2026-03-09