agentleFS
Sign inStart free
x0cx0c/agent-doc-skills/doc-init/SKILL.md

doc-init

Skill2 starsChanged 50 days agoMITView on GitHub

Establish or refresh project documentation coverage and install the global documentation lifecycle preset. Use for missing documentation structure, stale domain coverage, or a missing/outdated global documentation contract.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 1

    1. x0c/doc-skills★ 2100% same

    Edited · 0

    None found.

    Wrote their own version · 1

    1. daikubo-jb/my-claude-harness★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Global preset installation/upgrade: read the global-file discovery and upgrade sections of maintenance workflow.

    line 12
  2. Distinctive:

    Project creation or takeover: read the project workflow in maintenance workflow.

    line 13
  3. Distinctive:

    Existing project coverage refresh: use the affected-domain sections of that workflow.

    line 14
  4. Distinctive:

    Read workflow references only when the selected phase needs them.

    line 16
  5. Distinctive:

    Verify product truth, doc reachability, portable paths, content-summary navigation, conflicts and the actual runtime path when applicable.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Documentation initialization

Establish missing project documentation or refresh stale coverage. Follow the installed documentation lifecycle; environment instructions own language, memory, permissions, release, model selection and paths. Use agents-md-edit for deliberate AGENTS.md changes. Delegate only under current user authorization.

Choose the work

  • Global preset installation/upgrade: read the global-file discovery and upgrade sections of maintenance workflow. Discover real global targets and use scripts/insert_doc_governance.py; never inject into a product AGENTS.md.
  • Project creation or takeover: read the project workflow in maintenance workflow. Discover declared standards, existing docs and real domain boundaries before generating material. Record durable decisions before implementation.
  • Existing project coverage refresh: use the affected-domain sections of that workflow. Prefer current authoritative documents; do not regenerate unrelated coverage.

Read workflow references only when the selected phase needs them. Code, logs, database evidence, Git history and user decisions serve different questions; apply the workflow's evidence and data-safety boundaries rather than reading every source by default.

Completion

Verify product truth, doc reachability, portable paths, content-summary navigation, conflicts and the actual runtime path when applicable. Report covered domains, remaining limits and any source changes. No unverified requirement is adopted merely because it appears in a template.

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.

Check your setup, free