coleam00

coleam00/Archon

Command Claude Code

E2E test command — echoes back the user message.

coleam00/Archon

Command Claude Code

Review the PR for code quality, CLAUDE.md compliance, project conventions, and bugs (Pi-tuned).

coleam00/Archon

Command Claude Code

Review the PR's added/modified comments and docstrings for accuracy, value, and long-term maintainability (Pi-tuned).

coleam00/Archon

Command Claude Code

Review whether the PR's user-facing changes (APIs, CLI flags, env vars, behavior) are reflected in documentation (Pi-tuned).

coleam00/Archon

Command Claude Code

Review the PR for error-handling correctness — surfaced errors, no silent swallows, consistent error patterns (Pi-tuned).

coleam00/Archon

Command Claude Code

Produce the final summary of a maintainer-review-pr run for the workflow log.

coleam00/Archon

Command Claude Code

Synthesize findings from all review aspects into a single maintainer-ready review report (Pi-tuned).

coleam00/Archon

Command Claude Code

Review the PR for test coverage — does new behavior have tests, are critical paths exercised, do existing tests still cover what they should (Pi-tuned).

coleam00/Archon

Command Claude Code

Synthesize the maintainer's morning standup brief from gathered git/PR/issue/state data.

coleam00/Archon

Command Claude Code

Implement the requested work in this repository and keep going until it is complete and the focused checks on what you changed pass. You run inside a loop: each turn continues the same piece of work in the same session until you declare it done. You are a core maintainer of this codebase and you own the outcome of…

coleam00/Archon

Command Claude Code

Establish the proven causal chain for the target — from the observed symptom to the root cause that actually explains it — and write a report a fixer or planner can act on without repeating your work. You change nothing and fix nothing: the repository must be exactly as you found it when you finish. No one watches the…

coleam00/Archon

Command Claude Code

Turn the decided intent into a plan a competent implementer could execute without asking questions. You decide the approach — the plan records decisions, not options. You build nothing: the repository must be exactly as you found it when you finish.

coleam00/Archon

Command Claude Code

Prepare a clear, reviewer-friendly pull request for the committed work on the current branch. You never modify source files, and you never push, create, edit, or comment on the pull request yourself: your one write is the body file below. The node that follows pushes the branch and performs the one public write…

coleam00/Archon

Command Claude Code

Find defects the change introduces. Do not grade the code, summarize the diff, or reward activity. You are read-only: never modify files, commit, or post anywhere. Never edit this checkout, not even to revert: sibling reviewers read it at the same time, and the engine fails a reviewer that leaves it changed. Try a…

coleam00/Archon

Command Claude Code

Find this class of defect: after this change, someone following the repository's documentation would form a materially wrong expectation or lack a required step. Wrong documentation is worse than missing documentation; unnecessary documentation is maintenance debt. Read-only: never modify files, commit, or post…

coleam00/Archon

Command Claude Code

Find either defect: a real failure crosses the changed code and becomes indistinguishable from success to the caller, operator, or user who must react; or it escapes its owning item and aborts independent work. Not every error needs logging; recovery is correct when the contract permits it and the right owner can…

coleam00/Archon

Command Claude Code

Establish exactly what this review round examines, and write it down for the reviewer or reviewers that follow. You do not judge anything; you make the target precise.

coleam00/Archon

Command Claude Code

Hunt this defect class wherever the change exposes it, in any language: a type is missing at a seam, and something downstream pays for it — a parser that mis-reads, a hand-synced copy of a set, type, or table whose owner it could import or derive from, a second route that skips the validator, a value that silently…

coleam00/Archon

Command Claude Code

Produce one evidence-based verdict and write the review report humans read. You are read-only: never modify project files, commit, or write anything outside the artifacts directory. Read-only extends past the repository: a falsifying command creates its own scratch database and drops it, never writing to a configured…

coleam00/Archon

Command Claude Code

Find this class of defect: the change establishes or alters meaningful behavior, and no test would fail when that behavior regresses in a plausible way. Tests protect outcomes and invariants — count, lines, and coverage percentages are not outcomes. Read-only: never modify files, commit, or post anywhere. Never edit…

coleam00/Archon

Command Claude Code

Ground one dependency-update request against this repository as it exists right now, and decide whether an update is actually owed. You produce an assessment and a verdict; you change nothing. No one watches the run; the assessment file and your declared fields are the only things that persist.

coleam00/Archon

Command Claude Code

Confirm whether the work item still names real current work, judge whether it is a contract a run can start from, choose the kind of reasoning owed next, and stop. Write the decisive evidence and handoff to $ARTIFACTSDIR/triage.md. You assess and route only: the repository must be exactly as you found it when you…

coleam00/Archon

Command Claude Code

The project's gate ran and at least one check failed. $ARTIFACTSDIR/validation.md is the record: every check that ran, its group, its exit status, each failing check's output tail, and the path of each check's full output log. Decide why the failed checks failed, judging every one the record names. You fix nothing and…

coleam00/Archon

Command Claude Code

Find the project's own checks and declare them. You do not run the gate: a script runs exactly what you declare, for as long as it takes, and records every exit status. Your declaration is the whole of what gets validated, so it must be the project's gate and nothing else.