Menu

Individual skill

keep-why-repo-structure

Use when project documentation needs a layout or a knowledge item needs one home. Not for remote, credential, publish, deploy, or irreversible changes.

.devin/skills/keep-why-repo-structure/SKILL.md

Read pinned source

Source commit b0e8ce89a19fac880251dc3ea1babfeb4503a4fe

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
55
Repository last updated
Sep 28, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Keep why repo structure

## Contract

| Field | Bound contract |
|---|---|
| Trigger | Introducing or restructuring a project's documentation layout, or deciding which file a piece of project knowledge belongs in. |
| Authority | Reversible local: writes only the layout files this skill names, inside the local project; rollback is version control, restoring exactly the files this run touched. No remote mutation. Never deletes pre-existing files. Never commits, pushes, or publishes. |
| Side effect | Proposes layout only where nothing suitable exists: topic-indexed context files (auth.md, sync.md, by topic, never per-source-file or per-decision), a lean load-bearing index.md, a short landing README.md; entries are flat files with one line per applicable Type, Status, Evidence, Source, Revisit-when, grep-filterable, no rigid frontmatter schema. |
| Done | No near-duplicate topic files; index stays lean (detail loaded on relevance); every entry carries Status and Evidence at minimum; proportionality respected (sentence-level notes for self-evident choices); existing conventions preserved. |

## Inputs

- Required: a target project directory whose layout is being introduced or restructured, or a single item of project knowledge that needs a home.