Agent skill

Gsd Forensics

by SpillwaveSolutions in SpillwaveSolutions/agent-brain

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

MITAuto-check passedDevelopment

Install Gsd Forensics

skills CLI

$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-forensics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install SpillwaveSolutions/agent-brain gsd-forensics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/gsd-forensics .claude/skills/gsd-forensics && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "gsd-forensics" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-forensics into .claude/skills/gsd-forensics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-forensics", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-forensics

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-forensics -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install SpillwaveSolutions/agent-brain gsd-forensics --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/gsd-forensics .agents/skills/gsd-forensics && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "gsd-forensics" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-forensics into .agents/skills/gsd-forensics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-forensics", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-forensics -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install SpillwaveSolutions/agent-brain gsd-forensics --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/gsd-forensics .cursor/skills/gsd-forensics && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "gsd-forensics" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-forensics into .cursor/skills/gsd-forensics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-forensics", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/SpillwaveSolutions/agent-brain.git --path .codex/skills/gsd-forensics

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-forensics -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install SpillwaveSolutions/agent-brain gsd-forensics --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/gsd-forensics .gemini/skills/gsd-forensics && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "gsd-forensics" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-forensics into .gemini/skills/gsd-forensics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-forensics", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install SpillwaveSolutions/agent-brain gsd-forensics

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-forensics -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/gsd-forensics .github/skills/gsd-forensics && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "gsd-forensics" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-forensics into .github/skills/gsd-forensics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-forensics", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-forensics -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install SpillwaveSolutions/agent-brain gsd-forensics --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/gsd-forensics .opencode/skills/gsd-forensics && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "gsd-forensics" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-forensics into .opencode/skills/gsd-forensics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-forensics", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: gsd-forensics
GitHub stars: 120
Used in: 1 other repo
Token cost: ~1.1k tokens
SKILL.md length: 433 words
Files: 1
Skills in repo: 55
Repo updated: Sep 19, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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

Tasks that involve Git workflow
SKILL.md covers A. Skill Invocation, B. AskUserQuestion →… and C. Task() → spawn_agent Mapping
Calls git
Tasks that involve Runbooks and postmortems

What it does

Gsd Forensics is an agent skill from SpillwaveSolutions/agent-brain. Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow and Runbooks and postmortems. The repository describes itself as: Local-first RAG memory for AI agents: hybrid + GraphRAG search, MCP server with OAuth 2.1, plugin for Claude Code / OpenCode / Codex. The licence is MIT.

When your agent uses it

Tasks that involve Git workflow
Tasks that involve Runbooks and postmortems

Example prompts

“/gsd-forensics”

What it can do on your machine

Read from SKILL.md and the folder at commit 8339623. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gsd Forensics loads about 1.1k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 433 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~34
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from SpillwaveSolutions/agent-brain at commit 8339623, republished under its MIT licence (© SpillwaveSolutions). 433 words, ~1,072 tokens.

Download SKILL.mdSave it as .claude/skills/gsd-forensics/SKILL.md (or your agent's skills folder).

name: gsd-forensics
description: Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong
metadata.short-description: Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong

<codex_skill_adapter>

A. Skill Invocation

This skill is invoked by mentioning $gsd-forensics.
Treat all user text after $gsd-forensics as {{GSD_ARGS}}.
If no arguments are present, treat {{GSD_ARGS}} as empty.

B. AskUserQuestion → request_user_input Mapping

GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:

Parameter mapping:

header → header
question → question
Options formatted as "Label" — description → {label: "Label", description: "description"}
Generate id from header: lowercase, replace spaces with underscores

Batched calls:

AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

Multi-select workaround:

Codex has no multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.

Execute mode fallback:

When request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.

C. Task() → spawn_agent Mapping

GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:

Direct mapping:

Task(subagent_type="X", prompt="Y") → spawn_agent(agent_type="X", message="Y")
Task(model="...") → omit (Codex uses per-role config, not inline model selection)
fork_context: false by default — GSD agents load their own context via <files_to_read> blocks

Parallel fan-out:

Spawn multiple agents → collect agent IDs → wait(ids) for all to complete

Result parsing:

Look for structured markers in agent output: CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
close_agent(id) after collecting results from each agent </codex_skill_adapter>

<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> @/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/workflows/forensics.md </execution_context>

Show full SKILL.md (173 more words)Show less

<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: {{GSD_ARGS}} (optional — will ask if not provided)
```
</context>
```

<process>
Read and execute the forensics workflow from @/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/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>

Files

Just SKILL.md in .codex/skills/gsd-forensics of SpillwaveSolutions/agent-brain.

Open the folder on GitHubat commit 8339623

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in SpillwaveSolutions/agent-brain, which our catalogue first saw on October 7, 2026.

davepoon/buildwithclaudeplugins/gsd/skills/forensics

Compare with similar skills

Gsd Forensics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gsd Forensics compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Gsd Forensics this skillSpillwaveSolutions/agent-brain	120	1 repos	~1.1k	Automated safety check: Pass	MIT	18 days ago
GreptimeDB Release RunbookGreptimeTeam/greptimedb	6.7k	—	~1.4k	Automated safety check: Pass	Apache-2.0	2 days ago
Code Design Rationale Investigatorcursor/plugins	10k	9 repos	~2.6k	Automated safety check: Pass	None	yesterday
Simple Englishmoeru-ai/airi	50k	2 repos	~4.6k	Automated safety check: Pass	MIT	today
Mole CLI Release Flowtw93/Mole	69k	—	~2.5k	Automated safety check: Pass	GPL-3.0	yesterday
Hunk Release Workflowmodem-dev/hunk	9.5k	—	~3.8k	Automated safety check: Pass	MIT	yesterday

Similar skills

GreptimeDB Release Runbook
GreptimeTeam/greptimedb
Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.
6.7k GitHub stars~1.4k tokensUpdated 2 days ago
DevOps & CloudAuto-check passed
Code Design Rationale Investigator
cursor/plugins
Official
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
10k GitHub starsUsed in 9 repos~2.6k tokens
DevelopmentAuto-check passed
Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
50k GitHub starsUsed in 2 repos~4.6k tokens
DevelopmentAuto-check passed
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
69k GitHub stars~2.5k tokensUpdated yesterday
DevelopmentAuto-check passed
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
9.5k GitHub stars~3.8k tokensUpdated yesterday
DevelopmentAuto-check passed
Ansible Backport Creator
ansible/ansible
Creates backports of a merged Ansible devel pull request onto the right stable branches by cherry-picking its merge commit onto new backport branches.
71k GitHub stars~1.2k tokensUpdated yesterday
DevelopmentAuto-check passed

Questions about Gsd Forensics

What does Gsd Forensics do?

Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong. Gsd Forensics is an agent skill from SpillwaveSolutions/agent-brain.

When should I use Gsd Forensics?

Gsd Forensics fits situations like: tasks that involve Git workflow; tasks that involve Runbooks and postmortems.

How do I install Gsd Forensics in Claude Code?

Run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-forensics -a claude-code`. Or copy the skill folder (.codex/skills/gsd-forensics in SpillwaveSolutions/agent-brain) into .claude/skills/gsd-forensics in your project. Claude Code loads it when a task matches its description.

How do I install Gsd Forensics in Codex?

Run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-forensics -a codex`. Or copy the skill folder (.codex/skills/gsd-forensics in SpillwaveSolutions/agent-brain) into .agents/skills/gsd-forensics in your project. Codex loads it when a task matches its description.

Can I use Gsd Forensics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-forensics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gsd-forensics, .gemini/skills/gsd-forensics, .github/skills/gsd-forensics and .opencode/skills/gsd-forensics in your project.

What does Gsd Forensics need to run?

Going by SKILL.md and its folder, Gsd Forensics needs the command-line tools its instructions call (git).

Does Gsd Forensics access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Gsd Forensics safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gsd Forensics use?

Gsd Forensics is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gsd Forensics use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gsd Forensics?

Skills that share tags, products or a category with Gsd Forensics: GreptimeDB Release Runbook (GreptimeTeam/greptimedb, 6.7k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars), Simple English (moeru-ai/airi, 50k stars) and Mole CLI Release Flow (tw93/Mole, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gsd Forensics?

SpillwaveSolutions (a GitHub organization) maintains it in SpillwaveSolutions/agent-brain, which has 120 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on September 19, 2026.

Source: SpillwaveSolutions/agent-brain on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Gsd Forensics

Install Gsd Forensics

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

A. Skill Invocation

B. AskUserQuestion → request_user_input Mapping

C. Task() → spawn_agent Mapping

Files

Used in 1 other repository

Compare with similar skills

Similar skills

GreptimeDB Release Runbook

Code Design Rationale Investigator

Simple English

Mole CLI Release Flow

Hunk Release Workflow

Ansible Backport Creator

More from SpillwaveSolutions/agent-brain

Gsd Complete Milestone

Mastering Python Skill

Gsd Debug

Gsd Review Backlog

Configuring Agent Brain

Gsd Thread

Questions about Gsd Forensics

Install Gsd Forensics

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

A. Skill Invocation

B. AskUserQuestion → request_user_input Mapping

C. Task() → spawn_agent Mapping

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from SpillwaveSolutions/agent-brain

Related

Questions about Gsd Forensics