← ClaudeAtlas

yalla-auditlisted

Post-mortem diagnostic on a completed /yalla or /yalla-team run. Checks issue-based artifacts, PR evidence, review quality, and shipping discipline. Use after a run produced mediocre results, after a production incident traced to a yalla-shipped change, or periodically to improve the pipeline. Do NOT use during an active run.
iwo-szapar/yalla · ★ 1 · AI & Automation · score 77
Install: claude install-skill iwo-szapar/yalla
# /yalla-audit Inspect a completed run and produce prioritized findings with concrete fixes. Prefer GitHub issue/PR evidence and machine-readable artifacts over memory or prose. `$REPO` and `$BASE_BRANCH` come from `.claude/YALLA.md` (`repo:` / `base_branch:`), with `$REPO` auto-detected via `gh repo view --json nameWithOwner -q .nameWithOwner` when blank and `$BASE_BRANCH` defaulting to `main`. ## Input Requires an issue ID (`issue-###`, `###`) or PR number. If not provided, ask for one. ## Gathering Artifacts Use GitHub first: ```bash gh issue view ### --repo "$REPO" --json number,title,body,labels,assignees,state,url,closedAt,comments gh pr list --repo "$REPO" --state all --search "###" --json number,title,state,url,headRefName,baseRefName,body,comments gh pr view ### --repo "$REPO" --json number,title,body,state,headRefName,baseRefName,commits,comments,reviews,files gh pr checks ### --repo "$REPO" --json name,bucket,state,workflow,link ``` Also gather when present: - Plan file: `plans/active/issue-###-*` - Plan JSON: `plans/active/issue-###.plan.json` - Pipeline artifacts: `.pipeline/classification.json`, `.pipeline/diagnosis.json`, `.pipeline/acceptance-trace.json`, `.pipeline/test-evidence.json`, `.pipeline/review-results.json`, `.pipeline/ship-manifest.json` - Operator artifacts: `.pipeline/events.jsonl`, `.pipeline/latest-checkpoint.json`, `.pipeline/checkpoints/`, `.pipeline/report.html` - Long-running control artifacts: `.pipeline/goal-contract.json`, `.pip