agentleFS
RidhuanDEVRidhuanDEV/claude-skills/shadow-maintain/SKILL.md

shadow-maintain

Skill1 starsChanged yesterdayMITView on GitHub

Post-Production Maintenance & Incident RCA. Use when triaging live production incidents, conducting blameless postmortems/RCA, managing SLA/Harwat/OMKT backlogs, or shipping hotfixes with regression tests.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill after go-live during the warranty or Pemeliharaan & Perawatan (Harwat / OMKT) phase to manage production incidents, …

    line 8
  2. Very specific:

    When a P0 or P1 bug requires an urgent production fix:

    line 25
  3. Very specific:

    Stabilize First: If caused by the latest deploy, roll back immediately (/shadow-release) before debugging code.

    line 26
  4. Very specific:

    Write the smallest possible fix on a clean hotfix branch (fix/hotfix-<issue>).

    line 29
  5. Very specific:

    Mandatory: Add a regression test (/shadow-test) that fails without the fix and passes with the fix so the exact bug can never return …

    line 30
  6. Very specific:

    After every P0 or P1 incident, generate docs/incidents/RCA-YYYY-MM-DD-<slug>.md:

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Shadow Maintain (/shadow-maintain) — Post-Production Maintenance (Harwat), Incident RCA & SLA Governance

Use this skill after go-live during the warranty or Pemeliharaan & Perawatan (Harwat / OMKT) phase to manage production incidents, hotfixes, dependency patching, and monthly SLA reporting.


1. Severity Classification & SLA Response Matrix

SeverityDefinitionResponse / Triage TargetMitigation / Hotfix Target
P0 / Sev-1 (Critical Outage)Production down, login/payment/core workflow completely blocked, or active security/data breach.< 15 minutesRollback or hotfix within < 1–2 hours
P1 / Sev-2 (Major Degradation)Core feature broken for a subset of users/tenants with no easy workaround, or severe latency spike.< 30 minutesFix deployed within < 4–8 hours
P2 / Sev-3 (Moderate Bug)Non-critical bug or edge case with an operational workaround available.< 4 business hoursScheduled in next regular patch release (< 3–5 days)
P3 / Sev-4 (Minor / Cosmetic / Enhancement)UI alignment, wording tweak, or minor UX improvement.Next backlog groomingScheduled in monthly maintenance sprint

2. Production Hotfix Protocol (Zero-Regression Emergency Fix)

When a P0 or P1 bug requires an urgent production fix:

  1. Stabilize First: If caused by the latest deploy, roll back immediately (/shadow-release) before debugging code.
  2. Reproduce & Pinpoint Root Cause: Trace using requestId logs (/shadow-observe) and hand off causal diagnosis, minimal reproduction, and red-before/green-after hypothesis falsification to /shadow-debug (never treat a single log line as proven root cause).
  3. Minimal Surgical Patch + Regression Test:
    • Write the smallest possible fix on a clean hotfix branch (fix/hotfix-<issue>).
    • Mandatory: Add a regression test (/shadow-test) that fails without the fix and passes with the fix so the exact bug can never return silently.
  4. Verify & Document in Maintenance Log:
    • Record the commit SHA, before/after evidence screenshots, and resolution summary for the monthly Laporan Harwat (/shadow-doc).

3. Blameless Incident Postmortem (RCA Template)

After every P0 or P1 incident, generate docs/incidents/RCA-YYYY-MM-DD-<slug>.md:

  • Incident Summary & Customer Impact (Duration, affected requests/tenants, error budget consumed).
  • Timeline (UTC / WIB) (Detection time, escalation, mitigation applied, full recovery verified).
  • Root Cause & 5-Whys Analysis (Focus on systemic/architectural gaps, never blaming individuals).
  • What Went Well vs What Went Wrong (Why didn't automated tests or staging catch it?).
  • Corrective & Preventive Action Items (Concrete tasks with owner and priority: e.g., new alert rule, DB constraint, regression test).

4. Routine Preventive Maintenance Checklist (Monthly Harwat Cycle)

  • Corrective Maintenance: Resolving reported bugs/tickets with commit & screenshot evidence.
  • Adaptive Maintenance: OS/runtime security patches, expiring TLS certificate checks, third-party API adjustments.
  • Perfective Maintenance: Slow query index tuning (/shadow-db), disk/log cleanup, dependency security updates (npm/pip/composer audit), and monthly restore drill (/shadow-resilience).

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.