Skill Detail

Investigate repository failures with an evidence-backed Archon workflow

Run Archon’s bounded investigation workflow to reproduce a repository failure, establish its cause and hand off a saved evidence report before implementation.

Developer ToolsMulti-Framework
Developer Tools Multi-Framework Security Reviewed
⭐ 23.9k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill investigate-repository-failures-evidence-backed-archon-workflow Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Git; Archon; configured Claude Code, Codex or Pi provider; project reproduction dependencies
Install & setup
Install Archon using the upstream platform guide; the documented Homebrew route is brew install coleam00/archon/archon, followed by archon setup. Configure an authenticated Claude Code, Codex or Pi provider. In the target repository, use archon workflow list and confirm archon-investigate is available. Use a version containing the cited investigation contract; the inspected dev commit is 086aff57836fd0ba087f7ffeb5625a4c8a67c53e, and released versions may differ. Optional archon skill add installs agent guidance. No installation was executed during metadata review.
Author
coleam00
Publisher
Open Source
Last updated
Nov 13, 2026
Quick brief

Invoke this workflow when an agent needs to establish why a repository fails before someone implements a fix. Supply a repository checkout and one observable symptom, failing command, issue reference or question. Archon runs a defined investigation and preserves an evidence report for the next operator, rather than leaving the diagnosis only in chat.

How it works

What this skill actually does

After configuring Archon and a supported provider, confirm the bundled workflow with archon workflow list. From the repository, run archon workflow run archon-investigate "Why does the login test fail?", replacing the example with the actual target. Use archon workflow attention to inspect requests for an operator decision. Keep the investigation separate from implementation or delivery workflows.

The selected upstream workflow reads code, tests competing explanations and reproduces the symptom where feasible. Its declared result includes a verdict, summary and a pointer to investigation.md in the run artifacts. Retrieve and review that report: it should connect the symptom to concrete evidence, record reproduction commands or unavailable conditions, identify the fix boundary and disclose unresolved questions. A rooted, refuted or inconclusive result is valid; an inconclusive investigation is not proof that a bug is absent.

The workflow declares that it does not mutate the checkout and requires a nonempty report artifact. Treat this as the documented engine contract, not an independently tested security guarantee. The operator should check the saved report and repository state before handing the result to an implementation agent. The skill ends at diagnosis and a reviewable proposed fix; it does not authorize code changes, commits, issue comments, pull requests or merges.

Multi-Framework is appropriate because Archon intentionally runs Claude Code, Codex and Pi providers; no single runtime defines this investigation. Prerequisites are Git, Archon, a configured provider and the target project’s reproduction dependencies. Metadata and the pinned workflow/command sources were inspected; installation, provider execution and security were not tested. The pinned development source may be ahead of a packaged release, so confirm the installed workflow has this contract.