skills.rest
diShine-digital-agency
diShine-digital-agencyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

shine-forensics

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

1|Updated Apr 15, 2026
Search Tags:#debugging#root-cause#forensics#git-history#planning-state#workflow-diagnostics
One-click install
npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-forensics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shine-forensics
Source: https://github.com/diShine-digital-agency/SHINE-Code-System/tree/main/skills/shine-forensics
Command: npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-forensics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Forensic analysis of workflow runs
  • Trace artifacts and planning state to identify root causes
  • Optional remediation guidance

Quick Start

Run the forensics workflow to generate a diagnostic report from the current SHINE session.

Frequently Asked Questions about shine-forensics

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

FAQPage Schema
How do I diagnose a stalled SHINE workflow execution?▼

To diagnose a stalled SHINE workflow execution, analyze git history, planning artifacts, and workspace state to trace root causes. This generates a structured forensic report with remediation suggestions.

What is a post-mortem workflow diagnostic for failed git projects?▼

A post-mortem workflow diagnostic investigates failed or hung project runs by examining git logs and planning state. It identifies what went wrong and outputs a structured forensic report for prevention.

How do I trace root causes from git history and planning state?▼

Trace root causes by analyzing git logs and .planning state artifacts to reconstruct the workflow timeline. This isolates the exact failure point and generates targeted remediation guidance.

Does the forensic analysis preserve source integrity and redact sensitive data?▼

Yes, the forensic analysis preserves source integrity and redacts sensitive data during investigation. Results are written to .planning/forensics/ with optional issue creation to maintain a clean audit trail.

Can I automatically create issues from workflow forensics reports?▼

Yes, you can automatically create issues from workflow forensics reports. After analyzing git history and workspace state, the tool optionally generates issues alongside the diagnostic report in .planning/forensics/.

Related Skills

Explore More Data & Analytics Skills→
ThiagoVitaleThiagoVitale

gsd-forensics

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

Community
Advanced
D0NMEGAD0NMEGA
8

gsd-forensics

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

Community
Advanced
diShine-digital-agencydiShine-digital-agency
1

shine-debug

Diagnose persistent SHINE debugging sessions with structured root-cause reporting.

Community
Advanced
agentclashagentclash
25

git-rules

Validate git commit hygiene and working tree status post-commit.

Official
Basic