classify-change SKILL.md skillA
classify-change from appleboy/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add appleboy/skills/classify-change@git:20260613.5ad4cfbPins git:20260613.5ad4cfb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- appleboy/skills
- Path
plugins/classify-change/skills/classify-change/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260613.5ad4cfb, committed Jun 13, 2026
- First version recorded
- Apr 29, 2026
- Size
- 6,690 bytes
- Repository stars
- 23
- License
- none declared
Classify a proposed code change as Leaf Node or Core Code to decide how much AI usage and review rigor is appropriate. Use this skill whenever the user asks "is this leaf or core", "what kind of change is this", "should I vibe code this", "can AI write this", "how rigorous should the review be", or before starting any non-trivial change. Also useful as a sub-step inside other workflows (planning, PR prep, code review) when classification matters. Asks 6 diagnostic questions about propagation…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# classify-change The single most important rule for AI-assisted coding in production: confine the AI's mass output to leaf nodes, where the inevitable bit of tech debt won't propagate through the system. This skill makes the leaf-vs-core call concrete and consistent, so individual judgment doesn't drift across the team. ## When to use Use whenever the leaf-vs-core distinction matters. Triggers include: - "Is this leaf or core?" - "What classification is this change?" - "Should I vibe code this / can AI write this?" - "How carefully do I need to review this?" - Before starting non-trivial work, even when the user didn't ask - Before or during `plan-feature` or `pr-prepare`, when the leaf/core call should be explicit and consistent with this framework Skip only for changes that are obviously trivial (typo fixes, etc.). ## The two categories **Leaf node.** Code that nothing else depends on — feature endpoints, UI components, scripts, reports, one-off migrations. Failure is local. Tech debt here doesn't spread. Safe for high AI involvement, lighter review. …
Read the whole file at its exact version.
How to install
mdr add appleboy/skills/classify-change@sha256:03beb26b7055ddd4The line at the top of this page pins the label git:20260613.5ad4cfb, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qbybc7ke6drefged)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 29, 2026 and Jun 13, 2026, about one every 22 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260613.5ad4cfb latest | 2026-06-13 | 5ad4cfb | 6,690 B | A | view · diff |
| git:20260606.832a70a | 2026-06-06 | 832a70a | 6,722 B | A | view · diff |
| git:20260429.9a41119 | 2026-04-29 | 9a41119 | 6,558 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6690 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
appleboy/skills · 23 stars · license none declared · pushed 2026-09-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qbybc7ke6drefged GET https://markdownregistry.com/api/v1/resolve?ref=appleboy/skills/classify-change GET https://markdownregistry.com/api/v1/blob/03beb26b7055ddd44ca293712ddb814f6ed67151c04ca85f362139fc63b2d0f4
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.