skills.rest
FerroxLabs
FerroxLabsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ferrox-forensics

Diagnose failed Ferrox workflow executions from git history and planning artifacts.

21|9|Updated Jul 21, 2026
Search Tags:#git history#anomaly detection#forensics#planning artifacts#workflow diagnosis#ferrox
One-click install
npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-forensics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ferrox-forensics
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills/ferrox-forensics
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-forensics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill diagnoses failed, stuck, or unexpected Ferrox workflow executions by investigating git history, planning artifacts, and filesystem state so you can understand what went wrong and what to do next.

Core Features & Use Cases

  • Workflow Forensics: Reviews recent commits, status, diffs, and session artifacts to reconstruct the execution timeline.
  • Anomaly Detection: Checks for stuck loops, missing artifacts, abandoned work, and crash or interruption signals.
  • Actionable Reporting: Produces a structured forensic report with evidence-backed findings and recommendations, and can support deeper follow-up investigation.
  • Use Case: A phase stops progressing after a session break and you need a clear diagnosis of where the workflow diverged and whether recovery is possible.

Quick Start

Ask the skill to investigate the latest Ferrox run failure and summarize the root cause from the planning files and git history.

Frequently Asked Questions about ferrox-forensics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose a stuck or failed Ferrox workflow execution?▼

To diagnose a failed Ferrox workflow execution, you investigate git history, planning artifacts, and filesystem state to reconstruct the timeline and identify where the workflow diverged or stopped progressing.

What causes anomalous agent behavior or interrupted sessions in my workflow?▼

Anomalous agent behavior and interrupted sessions are caused by stuck loops, missing artifacts, or crash signals. Forensic analysis of session reports and commit diffs detects these execution anomalies.

Can I investigate post-mortem workflow failures without modifying my source files?▼

Yes, you can investigate post-mortem workflow failures without modifying source files. Forensic diagnosis reads .planning state files, commit history, and session reports exclusively to ensure project integrity.

How do I recover a workflow phase that stopped progressing after a session break?▼

To assess recovery for a stopped workflow phase, review recent commits, diffs, and planning artifacts to reconstruct the execution timeline and determine where the divergence occurred and if recovery is possible.

Related Skills

Explore More Software Engineering Skills→
D0NMEGAD0NMEGA
8

gsd-forensics

Analyze git history and planning artifacts to identify root causes of failed GSD workflows.

Community
Advanced
gesmith0606gesmith0606

gsd-forensics

Diagnose failed GSD workflows by analyzing git history and .planning artifacts.

Community
Advanced
joshua3403joshua3403

phase-8-review

Analyze a codebase for architecture consistency and convention adherence.

Community
Advanced
EhsaanArkEhsaanArk

investigate

Diagnose software bug root causes through phase-based investigation and code tracing.

Community
Advanced