agentleFS
Sign inStart free
buildomatorbuildomator/buildomator/skills/forensics/SKILL.md

forensics

Skill102 starsChanged 8 days agoMITView on GitHub

Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read and execute the forensics workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/forensics.md end-to-end.

    line 39
  2. Distinctive:

    Read-only investigation: Do not modify project source files during forensics.

    line 52
  3. Distinctive:

    Ground findings in evidence: Every anomaly must cite specific commits, files, or state data.

    line 54
  4. Distinctive:

    No speculation without evidence: If data is insufficient, say so — do not fabricate root causes.

    line 55

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<objective> Investigate what went wrong during a GSD workflow execution. Analyzes git history, `.planning/` artifacts, and file system state to detect anomalies and generate a structured diagnostic report.

Purpose: Diagnose failed or stuck workflows so the user can understand root cause and take corrective action. Output: Forensic report saved to .planning/forensics/, presented inline, with optional issue creation. </objective>

<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/forensics.md </execution_context>

<context> **Data sources:** - `git log` (recent commits, patterns, time gaps) - `git status` / `git diff` (uncommitted work, conflicts) - `.planning/STATE.md` (current position, session history) - `.planning/ROADMAP.md` (phase scope and progress) - `.planning/phases/*/` (PLAN.md, SUMMARY.md, VERIFICATION.md, CONTEXT.md) - `.planning/reports/SESSION_REPORT.md` (last session outcomes)

User input:

  • Problem description: $ARGUMENTS (optional — will ask if not provided)</context>
<process> Read and execute the forensics workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/forensics.md end-to-end. </process>

<success_criteria>

  • Evidence gathered from all available data sources
  • At least 4 anomaly types checked (stuck loop, missing artifacts, abandoned work, crash/interruption)
  • Structured forensic report written to .planning/forensics/report-{timestamp}.md
  • Report presented inline with findings, anomalies, and recommendations
  • Interactive investigation offered for deeper analysis
  • GitHub issue creation offered if actionable findings exist </success_criteria>

<critical_rules>

  • Read-only investigation: Do not modify project source files during forensics. Only write the forensic report and update STATE.md session tracking.
  • Redact sensitive data: Strip absolute paths, API keys, tokens from reports and issues.
  • Ground findings in evidence: Every anomaly must cite specific commits, files, or state data.
  • No speculation without evidence: If data is insufficient, say so — do not fabricate root causes. </critical_rules>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free