Core Principles

Expected outcome:

• a gap report
• a recommended mode (bootstrap or sync or none)
• a list of source-of-truth files and maintained paths

bootstrap

Use when:

• critical docs are missing
• there is no repository memory system
• the repository is new to the team or to the agent workflow

Expected outcome:

• minimal human docs or filled gaps in existing docs
• memory/knowledge/ skeleton
• .agent_memory/ local structure recommendation
• sync rules so future code changes update docs and memory

sync

Use when:

• docs and memory already exist
• code or contract files changed
• the repository likely drifted from its documentation or memory

Expected outcome:

• refreshed model memory
• targeted doc updates or a review list
• updated synchronization metadata

Decision Rules

Default mode selection:

1. If critical human docs or model-memory roots are missing, use bootstrap.
2. If they exist but source files changed, use sync.
3. If the repository looks mature and the user asked for assessment, use audit.
4. If the repository is already consistent and no change is needed, report that explicitly.

Do not treat every repo as needing a full bootstrap. Mature repos often need audit or a narrow sync.

Required Thinking Order

1. Identify repository shape.
2. Identify maintained path or primary execution path.
3. Identify source-of-truth files.
4. Decide which docs are human-facing and which memory files are model-facing.
5. Decide what should be git-tracked and what should stay local.
6. Only then scaffold or update files.

If the repository shape is unclear, read references/repo_shapes.md.

Human Docs vs Model Memory

Human docs usually include:

• README.md
• CONTRIBUTING.md
• CHANGELOG.md
• core runtime or architecture docs under docs/

Model memory usually includes:

• memory/knowledge/*.json
• memory/schemas/*.json
• local task or execution state under .agent_memory/

Read references/doc_policy.md before writing human docs. Read references/memory_policy.md before creating model memory. Read references/sync_rules.md before choosing what to refresh after code changes.

Minimal Bootstrap Target

Bootstrap only the smallest useful set. Usually that means:

• add or refine README.md
• add or refine CONTRIBUTING.md
• add or refine CHANGELOG.md
• add one core runtime or architecture doc if the repo needs it
• create memory/knowledge/
• create memory/schemas/
• add local .agent_memory/ directory guidance and ignore rules

Do not create extra files such as skill-local README guides or redundant summaries.

Source-of-Truth Hierarchy

Use this order when facts conflict:

1. runtime code and shared contracts
2. tests that enforce current behavior
3. maintained architecture docs
4. README and contribution rules
5. changelog entries
6. derived memory

If derived memory disagrees with code or shared contracts, update memory.

Scripts

Use the bundled scripts when they help:

• scripts/detect_repo_shape.py
  • summarize repository shape, entry points, docs, tests, and code layout
• scripts/audit_repo.py
  • report readiness gaps and recommend a mode
• scripts/bootstrap_repo.py
  • create missing standardization files conservatively
• scripts/build_knowledge_memory.py
  • build or refresh model-facing knowledge cards
• scripts/sync_repo.py
  • refresh knowledge memory and highlight doc review targets

Use script output as evidence, not as unquestioned truth. Review the results before finalizing changes.

Bootstrap Workflow

1. Run scripts/detect_repo_shape.py.
2. Identify maintained paths, entry points, and core contracts.
3. Check whether README.md, CONTRIBUTING.md, CHANGELOG.md, and memory/knowledge/ exist.
4. Create only the missing or clearly inadequate pieces.
5. Materialize initial knowledge cards with scripts/build_knowledge_memory.py.
6. Add or update ignore rules for local memory.
7. Summarize what future code changes must sync.

Sync Workflow

1. Identify changed source-of-truth files.
2. Refresh derived knowledge memory.
3. Update only docs whose facts are affected.
4. Update changelog when user-facing behavior, architecture, or contract semantics changed.
5. Report what was refreshed automatically and what still needs human review.

Audit Workflow

1. Report repository shape and maintained path candidates.
2. Report missing docs and memory.
3. Report likely source-of-truth files.
4. Recommend bootstrap, sync, or none.
5. If the user wants changes, continue with the recommended mode.

Quality Bar

• Docs must mention real modules, not placeholders.
• Memory must include source paths and a staleness rule.
• Generated content must be specific to the repository.
• Local memory must not leak secrets or raw chat transcripts.
• If the repository already has a strong standard, align with it instead of replacing it.

When Not To Use

Do not use this skill for:

• a one-file scratch script
• vendored or third-party code you should not standardize
• archived logs or generated outputs
• pure implementation work in a repo that already has good docs and memory, unless drift is suspected

Example Requests

• "Audit this repository and tell me whether it needs bootstrap or sync."
• "Standardize this repo for both humans and AI agents."
• "Create the initial docs and memory skeleton for this project."
• "Sync the repository docs and memory after the recent refactor."