adversarial-qa
Exploratory QA of a running feature through its UI (Playwright) and/or API (curl) to find issues the plan and committed tests…
Fills a workflow-retro record's Cost section with tokens, wall-clock time and handoff cost parsed from Claude Code session transcripts by a bundled read-only script. Use after /workflow-retro, while the transcripts still exist (pruned after about 30 days).
Claude Code
$ npx -y skills add cunhaax/ai-workflow --skill workflow-inspect --agent claude-code
Codex
$ npx skills add cunhaax/ai-workflow --skill workflow-inspect -a codex -y
Cursor
$ npx skills add cunhaax/ai-workflow --skill workflow-inspect -a cursor -y
Gemini CLI
$ npx skills add cunhaax/ai-workflow --skill workflow-inspect -a gemini-cli -y
GitHub Copilot
$ npx skills add cunhaax/ai-workflow --skill workflow-inspect -a github-copilot -y
OpenCode
$ npx skills add cunhaax/ai-workflow --skill workflow-inspect -a opencode -y
Windsurf
$ npx skills add cunhaax/ai-workflow --skill workflow-inspect -a windsurf -y
name: workflow-inspect
description: >
Fills a workflow-retro record's Cost section with tokens, wall-clock time
and handoff cost parsed from Claude Code session transcripts by a bundled
read-only script. Use after /workflow-retro, while the transcripts still
exist (pruned after about 30 days).
license: MIT
compatibility: Requires python3 and Claude Code session transcripts under ~/.claude/projects/.
allowed-tools: Bash(python3 ${CLAUDE_SKILL_DIR}/inspect.py *)
metadata:
author: André CunhaFill a `/workflow-retro` record's pending `## Cost` section with numbers computed from the raw session transcripts: tokens and wall-clock per sub-agent, sub-agents' share of the total, and the handoff tax (files the planner read that the main agent re-read). Run after `/workflow-retro`, within the transcript retention window.
re-inspection`
transcripts, prints markdown to stdout)
a figure the script didn't print. Script fails or its output carries warnings → surface them to the user as-is (`AGENTS.md` Rule 2 applies)
the chosen record(s), after the user confirms. The one other edit allowed is adding session IDs to the record's `Sessions:` line (step 4), also after the user confirms. Never commit anything; `.workflow-log/` stays local
worktree (parent of `git rev-parse --path-format=absolute --git-common-dir`)
re-inspection` (sessions were added after the last inspect; Step 5 replaces the whole section, marker included)
unrecoverable once transcripts are pruned. With the user's confirmation, close the section with `unavailable — transcripts pruned or session IDs unknown` instead of leaving `pending` forever
One command, from the repository root:
python3 ${CLAUDE_SKILL_DIR}/inspect.py <session-id> [<session-id> …]The script:
`~/.claude/projects/` (transcripts are filed under the session's *launch* directory, not necessarily the worktree; never derive the directory from a path)
output, and the numbers are then lower bounds
Before writing, act on the output:
record** → the feature spanned more sessions than the retro knew. Offer to add those IDs to the record's `Sessions:` line and re-run the script once with the full list
than the Steps table's review rounds) → point out the discrepancy to the user. The outcome sections are theirs to amend; never edit them yourself
included) with it, leave every other section untouched, report the file path
Turns Claude Code into a small development team instead of one agent guessing alone — with a git-level gate that keeps the humans in charge of what actually ships.
Exploratory QA of a running feature through its UI (Playwright) and/or API (curl) to find issues the plan and committed tests…
Reviews code changes against project standards and the approved plan; returns PASS/FAIL/NEEDS_DECISION per checklist item plus…
Runs the full AI-assisted workflow for a non-trivial feature or change: plan, plan critique, user approval, implementation with…
Sets up and checks the AI workflow in a project that has this plugin installed: scaffolds missing AGENTS.md, CLAUDE.md, hooks,…
Critiques a draft implementation plan with pre-mortem, inversion, load-bearing-assumption and consistency checks; returns…
Drafts a structured implementation plan (approval summary with acceptance criteria, contract, files, edge cases, test strategy)…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.