agentleFS
jctotsjctots/thinkpad-fedora-agent/.claude/skills/incident/SKILL.md

incident

Skill0 starsChanged 3 months agoMITView on GitHub

Scaffold a new incidents/I{nnn}-{slug}.md from the template and insert its row in incidents/index.md. Use right after a fix lands on this machine — a broken thing that this session's work fixed. Not for decisions (alternatives weighed, no breakage) or host facts (firmware, device IDs) — those go elsewhere per incidents/index.md's own header.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use runbook, perf and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    runbook

    Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.

    Also in 4 projects that use this

  • MicrosoftSkill

    perf

    Speed and memory performance rules for Rust crates, the Node addon, webui-framework, and webui-delivery.

    Also in 3 projects that use this

  • drewdrewthisSkill

    sweep

    Search for similar patterns, anti-patterns, or issues elsewhere in the codebase after a fix or feature. Use after implementing a fix to catch the same bug in other places, or proactively to audit for a known pattern.

    Also in 3 projects that use this

  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    Also in 5 projects that use this

  • mijunriSkill

    database

    数据库脚本与操作规范。脚本放在 db_scripts 目录,遵循查询优化、事务、安全等实践。

    Also in 3 projects that use this

  • tuistSkill

    migrate

    Migrates existing Xcode projects to Tuist generated workspaces with build and run validation, external dependency mapping, and migration checklists. Use when adopting Tuist for an existing app or converting a hand-edited Xcode project to generated projects.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write the entry when the problem is fixed, not at the end of the session — CLAUDE.md and incidents/index.md both call this out: the failed …

    line 6
  2. Very specific:

    Determine the next number: Read incidents/index.md's table, take the highest existing I{nnn}, increment.

    line 11
  3. Distinctive:

    Don't skip it.

    line 28
  4. Very specific:

    If the fix also touched anything under /etc, this is also a natural moment to run /etc-drift — the two often go together.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “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

Write the entry when the problem is fixed, not at the end of the session — CLAUDE.md and incidents/index.md both call this out: the failed attempts are the part that's gone forever if it's left until later. Run this proactively, right after landing a fix, without waiting to be asked.

  1. Determine the next number. Read incidents/index.md's table, take the highest existing I{nnn}, increment. Don't guess or reuse a number.
  2. Create incidents/I{nnn}-{slug}.md from incidents/_template.md. Fill every field from what actually happened this session, not a generic description:
    • Area — one of the fixed vocabulary in the template's header comment and the index's "Areas" section: rpm-ostree, flatpak, toolbox, gnome, hardware, network, etc, backup, agent, boot.
    • Symptom — what was observed, verbatim where possible (error text), not the diagnosis.
    • Cause / Fix — what turned out to be true, and the exact copy-pasteable fix.
    • Tried first — what didn't work and why it looked plausible. This is the field most likely to be skipped under time pressure and the one the template calls "usually the most valuable paragraph in the file." Don't skip it.
    • Reversibility — name the actual layer: rpm-ostree rollback, etckeeper diff, /var/home backup, or none (say what the exposure was if none).
    • Captured in — the script this incident got automated into, or not yet — still a one-off.
  3. The Tally line is always asked, never guessed: time-to-fix ~Nm · first proposal: right / wrong / n/a — agent unavailable. Ask the user for the first-proposal verdict rather than inferring it — this is the one field CLAUDE.md is explicit about not fabricating, since it's the evidence the project's central claim rests on. An index with no ✗ is evidence of nothing except selective writing; don't round a wrong first guess up to a right one out of politeness.
  4. Insert the row into incidents/index.md — newest first, at the top of the table, matching the existing column order.
  5. If the fix also touched anything under /etc, this is also a natural moment to run /etc-drift — the two often go together.

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.