agentleFS
45ck45ck/maintenance-evolution-skills/.claude/skills/hotfix-vs-patch-vs-version-update-selector/SKILL.md

hotfix-vs-patch-vs-version-update-selector

Skill2 starsChanged 8 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer operationally useful artifacts over generic “maintenance best practices.”

    line 53
  2. Distinctive:

    Keep outputs concise enough to drop into tickets, incident notes, PRs, or runbooks.

    line 56
  3. Distinctive:

    Do not confuse a symptom with a verified root cause.

    line 59
  4. Distinctive:

    Do not recommend shipping changes without considering rollback and regression exposure.

    line 60
  5. Distinctive:

    Do not hide environment or data dependencies that could invalidate the result.

    line 61
  6. Distinctive:

    Do not treat all maintenance work as “just bug fixing.”

    line 62

≈ “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

hotfix-vs-patch-vs-version-update-selector

Purpose

Select whether an issue should be handled as a hotfix, normal patch, or broader version update based on urgency and blast radius.

Trigger this skill when

  • A maintenance, support, defect, release, or evolution decision needs clearer structure.
  • Symptoms, causes, impacts, and release choices are being conflated.
  • You need artifacts that reduce operational surprise and rework.

Expected inputs

  • issue report or change request
  • system context
  • known symptoms or requested change
  • constraints / urgency
  • available evidence if any

Deliverables

  • summary
  • findings
  • structured outputs
  • risks / blockers
  • open questions
  • recommended next skill

Operating procedure

  1. Clarify whether the work is driven by a defect, environmental change, requested improvement, or preventive maintenance need.
  2. Separate observations, assumptions, hypotheses, and verified facts.
  3. Produce the skill-specific artifact or decision aid.
  4. Surface blast radius, rollback needs, regression exposure, and consumer impact explicitly.
  5. Recommend the next best handoff instead of trying to solve the entire maintenance lifecycle at once.

Quality gates

  • The output is specific to the current maintenance context.
  • Uncertainty, evidence gaps, and operational constraints are visible.
  • The result is usable by an engineer, maintainer, on-call responder, or team lead.
  • The output improves safety, speed, or clarity of the next maintenance decision.

Handoff targets

  • rollback-plan-writer
  • deprecation-planner
  • migration-readiness-checker

Output style

  • Prefer operationally useful artifacts over generic “maintenance best practices.”
  • Be explicit about urgency, blast radius, rollback risk, and residual uncertainty.
  • Surface what still needs verification instead of implying the cause is proven.
  • Keep outputs concise enough to drop into tickets, incident notes, PRs, or runbooks.

Failure modes to avoid

  • Do not confuse a symptom with a verified root cause.
  • Do not recommend shipping changes without considering rollback and regression exposure.
  • Do not hide environment or data dependencies that could invalidate the result.
  • Do not treat all maintenance work as “just bug fixing.”

Minimum output skeleton

## Summary
## Findings
## Structured outputs
## Risks / blockers
## Open questions
## Recommended next skill

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.