菜单
Query code quality status from pitchfork background watchers (tests, lint, typecheck, format). Use when you want to check if tests pass, code is formatted, or lint is clean — without running checks manually.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Browser automation via agent-browser. Use when the user wants to browse, interact with, or inspect web pages.
Review agent-facing knowledge (rules, AGENTS.md, CONVENTIONS.md, README.md, domain docs) for staleness and accuracy. Use when the user asks to audit, clean, or prune knowledge. Also use when they're confused by a rule/doc that seems wrong — treat that as the starting point for a broader audit.
Reflect on session, update rules, commit with jj.
Adversarial design interview.
Ingest sources into the wiki.
Wiki health checks.
| name | pitchfork |
| description | Query code quality status from pitchfork background watchers (tests, lint, typecheck, format). Use when you want to check if tests pass, code is formatted, or lint is clean — without running checks manually. |
Background daemons that run code quality checks on file change. Check status instead of running commands manually.
pitchfork list # all daemons, status, health
pitchfork logs <daemon> --raw -n 50 # latest output
pitchfork logs --raw -n 30 # all logs at once
pitchfork logs <daemon> --raw --since 5min # recent only (avoid stale logs)
pitchfork start --all # start all
pitchfork restart <daemon> # restart stale daemon
pitchfork stop --all # stop all
pitchfork logs --clear # clear history for fresh session
Daemons are defined in pitchfork.toml at project root.
Empty output = clean. No lines means last run passed.
Otherwise read raw logs directly:
FAIL/PASS summary at bottomerror TS... linespitchfork logs <daemon> --raw --since 5minAlways use --since to avoid stale errors from previous runs. Clear history with --clear for fresh sessions.