What does SCAR stand for?

SCAR stands for Signal (observed symptom), Cause (root cause analysis), Action (the fix applied), and Reinforcement (steps taken to prevent recurrence).

Can I use this for simple bugs or only major incidents?

The skill supports both. It helps classify the issue as a 'Bug' or an 'Incident' based on impact and urgency, applying the appropriate documentation depth for each.

Where are the incident reports stored?

Reports are saved as structured Markdown files within your project's wiki or incidents directory, ensuring they are version-controlled and easily searchable.

Does it suggest automated actions?

Yes, after documentation, it can suggest specific tests to write, guardrails to implement in code, or update your project's index files automatically.

How does this skill handle recurring bugs?

It searches existing logs first. If a similar incident is found, it updates the existing file and escalates the Reinforcement level, moving from simple documentation to automated tests or code guardrails.

SCAR Incident Documentation

Name: SCAR Incident Documentation
Author: giobi

bygiobi

0•

생산성 및 워크플로

Implements the S.C.A.R. framework to document bugs and incidents through Signal, Cause, Action, and Reinforcement analysis.

The SCAR skill provides a structured methodology for Claude to assist developers in documenting technical incidents and bug fixes. By guiding users through the Signal, Cause, Action, and Reinforcement phases, it ensures that every issue results in a permanent system improvement. It features automatic duplicate detection, recurrence tracking with escalation levels (from documentation to automated tests), and standardized markdown reporting, helping teams build a resilient internal knowledge base or wiki of technical challenges and their solutions.

주요 기능

01Automated Categorization: Distinguishes between immediate incidents and potential bugs for better prioritization.

02S.C.A.R. Framework Guidance: Step-by-step walkthrough for Signal, Cause, Action, and Reinforcement analysis.

03Structured Wiki Generation: Produces standardized Markdown files with metadata and tags for easy indexing.

040 GitHub stars

05Escalation Logic: Increases the strength of prevention (Reinforcement) if an incident reoccurs.

06Recurrence Detection: Automatically searches project wikis for existing incidents to prevent duplicate documentation.

사용 사례

01Documenting a critical production outage to prevent future occurrences using the 5 Whys method.

02Managing a technical debt wiki by tracking recurring infrastructure issues and escalating guardrails.

03Conducting a root cause analysis after a complex bug fix to identify structural weaknesses.

주요 기능

01Automated Categorization: Distinguishes between immediate incidents and potential bugs for better prioritization.

02S.C.A.R. Framework Guidance: Step-by-step walkthrough for Signal, Cause, Action, and Reinforcement analysis.

03Structured Wiki Generation: Produces standardized Markdown files with metadata and tags for easy indexing.

040 GitHub stars

05Escalation Logic: Increases the strength of prevention (Reinforcement) if an incident reoccurs.

06Recurrence Detection: Automatically searches project wikis for existing incidents to prevent duplicate documentation.

사용 사례

01Documenting a critical production outage to prevent future occurrences using the 5 Whys method.

02Managing a technical debt wiki by tracking recurring infrastructure issues and escalating guardrails.

03Conducting a root cause analysis after a complex bug fix to identify structural weaknesses.