Skip to content

YurunChen/repo-docs-skills / docs

repo-docs

Flagged

Build and maintain a Markdown guide that helps humans understand a repository through real behavior, concepts, and evidence. Use when a user asks to understand a repo, generate or update repo-docs, answer repo-architecture/onboarding questions, seed docs for a new project, sync docs after code changes, or delete generated repo docs.

FileKindSize
.nojekyllother0 B
EXAMPLES.mdmarkdown33.1 KB
PAGE_RULES.mdmarkdown44.2 KB
QUALITY_RULES.mdmarkdown4.8 KB
README.mdmarkdown8.9 KB
README_CN.mdmarkdown8.6 KB
REFERENCE.mdmarkdown1.0 KB
ROOT_AGENT_RULES.mdmarkdown4.2 KB
SCOPE_MODES.mdmarkdown4.9 KB
SKILL.mdskill md12.4 KB
SYNC_RULES.mdmarkdown20.5 KB
WRITING.mdmarkdown15.0 KB
assets/gsap.min.jsscript70.7 KB
assets/logo.pngbinary284.0 KB
assets/main.pngbinary1.9 MB
assets/repo-docs-evidence-atlas.pngbinary2.1 MB
assets/repo-docs-pixel-kingdom.pngbinary2.6 MB
assets/repo-docs-pixel-workshop.pngbinary2.4 MB
assets/site.cssother63.7 KB
assets/site.jsscript38.6 KB
case-studies/aider.mdmarkdown1.2 KB
case-studies/bolt-diy.mdmarkdown1.2 KB
case-studies/generated/aider/repo-docs/README.mdmarkdown3.7 KB
case-studies/generated/aider/repo-docs/change-log.mdmarkdown1.4 KB
case-studies/generated/aider/repo-docs/code-map.mdmarkdown3.5 KB
case-studies/generated/aider/repo-docs/glossary.mdmarkdown3.3 KB
case-studies/generated/aider/repo-docs/modules/edit-lifecycle.mdmarkdown3.1 KB
case-studies/generated/aider/repo-docs/modules/session-assembly.mdmarkdown2.3 KB
case-studies/generated/aider/repo-docs/references/quality-review.mdmarkdown3.7 KB
case-studies/generated/aider/repo-docs/references/source-evidence.mdmarkdown13.0 KB
case-studies/generated/aider/repo-docs/walkthroughs/one-real-run.mdmarkdown10.4 KB
case-studies/generated/bolt-diy/repo-docs/README.mdmarkdown3.9 KB
case-studies/generated/bolt-diy/repo-docs/change-log.mdmarkdown1.5 KB
case-studies/generated/bolt-diy/repo-docs/code-map.mdmarkdown4.1 KB
case-studies/generated/bolt-diy/repo-docs/glossary.mdmarkdown3.5 KB
case-studies/generated/bolt-diy/repo-docs/modules/chat-api-contract.mdmarkdown5.5 KB
case-studies/generated/bolt-diy/repo-docs/modules/chat-stream.mdmarkdown2.7 KB
case-studies/generated/bolt-diy/repo-docs/modules/provider-model-selection.mdmarkdown2.8 KB
case-studies/generated/bolt-diy/repo-docs/references/quality-review.mdmarkdown3.2 KB
case-studies/generated/bolt-diy/repo-docs/references/source-evidence.mdmarkdown11.1 KB
case-studies/generated/bolt-diy/repo-docs/walkthroughs/one-real-run.mdmarkdown8.6 KB
case-studies/generated/tabby/repo-docs/README.mdmarkdown2.6 KB
case-studies/generated/tabby/repo-docs/change-log.mdmarkdown1.7 KB
case-studies/generated/tabby/repo-docs/code-map.mdmarkdown4.4 KB
case-studies/generated/tabby/repo-docs/glossary.mdmarkdown4.3 KB
case-studies/generated/tabby/repo-docs/modules/completion-contract.mdmarkdown9.6 KB
case-studies/generated/tabby/repo-docs/modules/completion-pipeline.mdmarkdown2.3 KB
case-studies/generated/tabby/repo-docs/modules/retrieval-context.mdmarkdown3.2 KB
case-studies/generated/tabby/repo-docs/references/quality-review.mdmarkdown3.2 KB
case-studies/generated/tabby/repo-docs/references/source-evidence.mdmarkdown10.2 KB
case-studies/generated/tabby/repo-docs/walkthroughs/one-real-run.mdmarkdown9.6 KB
case-studies/tabby.mdmarkdown1.2 KB
index.htmlother26.1 KB
scripts/validate_repo_docs.pyexecutablescript46.6 KB
validate_repo_docs.pyscript482 B

index.html

View on GitHub
<!doctype html>
<html lang="en">
  <head>
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <title>Repo-Docs — Keep up with the code your agents write.</title>
    <meta
      name="description"
      content="Repo-Docs helps turn real coding runs into small, source-backed pages that stay beside the repository."
    />
    <meta property="og:title" content="Repo-Docs — Keep up with the code your agents write." />
    <meta
      property="og:description"
      content="A source-backed guide for agent-built code. Start with understanding, then follow the paths."
    />
    <meta property="og:image" content="assets/repo-docs-pixel-kingdom.png" />
    <link rel="icon" href="assets/logo.png" />
    <link rel="preload" as="image" href="assets/repo-docs-pixel-kingdom.png" fetchpriority="high" />
    <link rel="preconnect" href="https://fonts.googleapis.com" />
    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
    <link
      href="https://fonts.googleapis.com/css2?family=Spectral:ital,wght@0,500;0,600;0,700;1,500&family=Source+Sans+3:ital,wght@0,400;0,500;0,600;0,700;1,400&display=swap"
      rel="stylesheet"
    />
    <link rel="stylesheet" href="assets/site.css?v=20260628-reference-site-polish3" />
  </head>
  <body>
    <div class="pixel-toast" role="status" aria-live="polite"></div>
    <a class="skip-link" href="#main">Skip to content</a>

    <header class="site-nav" aria-label="Primary navigation">
      <a class="brand" href="#top" aria-label="Repo-Docs home">
        <img src="assets/logo.png" alt="" width="735" height="703" />
        <span>Repo-Docs</span>
      </a>
      <nav class="nav-links" aria-label="Sections">
        <a href="#map">Map</a>
        <a href="#cases">Cases</a>
        <a href="#artifacts">Artifacts</a>
        <a href="#quests">Modes</a>
        <a href="#contribute">Contribute</a>
      </nav>
      <div class="nav-utility">
        <div class="language-switch" role="group" aria-label="Language">
          <button type="button" data-lang-switch="en" aria-pressed="true">EN</button>
          <button type="button" data-lang-switch="zh" aria-pressed="false">中文</button>
        </div>
        <a class="nav-action" href="README.md">Docs</a>
      </div>
    </header>

    <main id="main">
      <section class="hero-atlas hero-atlas--kingdom" id="top" aria-labelledby="hero-title">
        <div class="hero-atlas__veil" aria-hidden="true"></div>
        <div class="hero-atlas__content">
          <div class="hero-copy">
            <p class="eyebrow">
              <span class="eyebrow-pip" aria-hidden="true"></span>
              <span class="eyebrow-text">A source-backed guide for agent-built code.</span>
            </p>
            <h1 id="hero-title">
              <span class="hero-serif">Keep up with the code</span>
              <span class="hero-pixel">your agents write.</span>
            </h1>
            <p class="hero-lead">
              When code moves quickly, context is easy to leave behind. Repo-Docs helps you turn one
              real run into a few clear pages that live with the source: walkthroughs, concepts,
              evidence, and sync notes.
            </p>
            <p class="hero-aside">Start with understanding, then follow the paths.</p>

            <div class="hero-install" aria-label="Install prompt">
              <div class="hero-install-top">
                <span class="install-prompt-label">repo-docs install prompt</span>
                <button class="button button-copy" type="button" data-copy-install aria-label="Copy install prompt">Copy</button>
              </div>
              <pre><code id="install-snippet-code" data-install-snippet>Install the repo-docs skill from this project:
https://github.com/YurunChen/repo-docs-skills

Make both repo-docs and repo-docs-zh available
in my agent skill directory.</code></pre>
            </div>

            <div class="hero-actions" aria-label="Primary actions">
              <a class="button button-primary" href="#cases">See generated docs</a>
              <a class="button button-secondary" href="https://github.com/YurunChen/repo-docs-skills">GitHub</a>
              <a class="button button-secondary" href="#contribute">Contribute</a>
            </div>

            <div class="agents-strip agents-strip--hero" aria-label="Compatible coding agents">
              <span class="agents-label">Works with</span>
              <ul>
                <li>Cursor</li>
                <li>Claude Code</li>
                <li>Codex</li>
                <li>Copilot</li>
                <li>Windsurf</li>
              </ul>
            </div>
          </div>
        </div>
      </section>

      <section class="contrast-band" id="contrast" aria-labelledby="contrast-title">
        <div class="contrast-head">
          <h2 id="contrast-title" class="contrast-title">Fast-moving code needs a place for context.</h2>
          <p class="contrast-lead">
            Repo-Docs is not a file-tree tour or a chat archive. It keeps a modest project guide
            beside the source, so the next person can see why things work instead of piecing it
            together from old messages.
          </p>
        </div>
        <div class="contrast-grid">
          <article class="contrast-card contrast-card--before">
            <span class="contrast-tag contrast-tag--dim">When context stays in chat</span>
            <ul>
              <li>The code changed, but the reason is hard to find later.</li>
              <li>There are many files, yet the real behavior path is still unclear.</li>
              <li>README, source, tests, and agent notes slowly drift apart.</li>
              <li>The next reader has to rediscover the same context again.</li>
            </ul>
          </article>
          <div class="contrast-bridge" aria-hidden="true">
            <span class="contrast-bridge-line"></span>
            <span class="contrast-bridge-node"></span>
          </div>
          <article class="contrast-card contrast-card--after">
            <span class="contrast-tag contrast-tag--bright">When context lives with source</span>
            <ul>
              <li>A walkthrough follows one real run from entry to output.</li>
              <li>Short concept pages name the ideas worth remembering.</li>
              <li>Evidence pages keep source proof and quality review easy to check.</li>
              <li>A sync note tells future agents when a page needs a small update.</li>
            </ul>
          </article>
        </div>
      </section>

      <section class="world-strip" aria-label="Repo-Docs operating promises">
        <article>
          <span>Start from a run</span>
          <strong>Follow one real behavior before making a file inventory.</strong>
        </article>
        <article>
          <span>Keep the evidence close</span>
          <strong>Commands, contracts, and source links stay with the explanation.</strong>
        </article>
        <article>
          <span>Update gently</span>
          <strong>When something changes, patch the page that owns it.</strong>
        </article>
      </section>

      <section class="section case-section case-section--featured" id="cases" aria-labelledby="case-title">
        <div class="case-copy">
          <p class="section-note">GitHub examples</p>
          <h2 id="case-title">A few real repositories, with the generated docs visible.</h2>
          <p>
            These examples come from public GitHub repositories that are not skill projects. Each
            panel shows the files Repo-Docs generated, and each file opens the Markdown content
            written from inspected source.
          </p>
        </div>

        <div class="case-tabs" role="tablist" aria-label="Case study repositories">
          <button type="button" role="tab" id="case-tab-aider" class="is-active" data-case-tab="aider" aria-selected="true" aria-controls="case-panel-aider">Aider-AI/aider</button>
          <button type="button" role="tab" id="case-tab-bolt" data-case-tab="bolt" aria-selected="false" aria-controls="case-panel-bolt">stackblitz-labs/bolt.diy</button>
          <button type="button" role="tab" id="case-tab-tabby" data-case-tab="tabby" aria-selected="false" aria-controls="case-panel-tabby">TabbyML/tabby</button>
        </div>

        <div class="case-showcase" aria-label="Repo-Docs generated file trees from public GitHub repos">
          <article class="case-repo-tree is-active" id="case-panel-aider" data-case-panel="aider" role="tabpanel" aria-labelledby="case-tab-aider">
            <div class="case-tree-head">
              <span>Aider-AI/aider</span>
              <strong>repo-docs/ CLI edit loop</strong>
              <a href="case-studies/aider.md">Open full case</a>
            </div>
            <div class="case-tree-split">
              <div class="case-tree-pane" aria-label="Generated file tree for Aider-AI aider">
                <div class="tree-node tree-root">repo-docs/</div>
                <div class="tree-branch">
                  <button class="tree-node tree-file" type="button" data-file="case-studies/generated/aider/repo-docs/README.md" data-title="README.md">README.md</button>
                  <div class="tree-node tree-folder">walkthroughs/</div>
                  <button class="tree-node tree-file tree-leaf is-active" type="button" data-file="case-studies/generated/aider/repo-docs/walkthroughs/one-real-run.md" data-title="walkthroughs/one-real-run.md" aria-current="true">one-real-run.md</button>
                  <button class="tree-node tree-file" type="button" data-file="case-studies/generated/aider/repo-docs/code-map.md" data-title="code-map.md">code-map.md</button>
                  <div class="tree-node tree-folder">modules/</div>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/aider/repo-docs/modules/session-assembly.md" data-title="modules/session-assembly.md">session-assembly.md</button>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/aider/repo-docs/modules/edit-lifecycle.md" data-title="modules/edit-lifecycle.md">edit-lifecycle.md</button>
                  <div class="tree-node tree-folder">references/</div>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/aider/repo-docs/references/source-evidence.md" data-title="references/source-evidence.md">source-evidence.md</button>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/aider/repo-docs/references/quality-review.md" data-title="references/quality-review.md">quality-review.md</button>
                  <button class="tree-node tree-file" type="button" data-file="case-studies/generated/aider/repo-docs/glossary.md" data-title="glossary.md">glossary.md</button>
                  <button class="tree-node tree-file" type="button" data-file="case-studies/generated/aider/repo-docs/change-log.md" data-title="change-log.md">change-log.md</button>
                </div>
              </div>
              <div class="case-file-preview" aria-live="polite">
                <span>walkthroughs/one-real-run.md</span>
                <div class="case-file-content case-markdown-content">Opening generated file...</div>
              </div>
            </div>
          </article>

          <article class="case-repo-tree" id="case-panel-bolt" data-case-panel="bolt" role="tabpanel" aria-labelledby="case-tab-bolt" hidden>
            <div class="case-tree-head">
              <span>stackblitz-labs/bolt.diy</span>
              <strong>repo-docs/ chat streaming path</strong>
              <a href="case-studies/bolt-diy.md">Open full case</a>
            </div>
            <div class="case-tree-split">
              <div class="case-tree-pane" aria-label="Generated file tree for stackblitz-labs bolt diy">
                <div class="tree-node tree-root">repo-docs/</div>
                <div class="tree-branch">
                  <button class="tree-node tree-file" type="button" data-file="case-studies/generated/bolt-diy/repo-docs/README.md" data-title="README.md">README.md</button>
                  <div class="tree-node tree-folder">walkthroughs/</div>
                  <button class="tree-node tree-file tree-leaf is-active" type="button" data-file="case-studies/generated/bolt-diy/repo-docs/walkthroughs/one-real-run.md" data-title="walkthroughs/one-real-run.md" aria-current="true">one-real-run.md</button>
                  <button class="tree-node tree-file" type="button" data-file="case-studies/generated/bolt-diy/repo-docs/code-map.md" data-title="code-map.md">code-map.md</button>
                  <div class="tree-node tree-folder">modules/</div>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/bolt-diy/repo-docs/modules/chat-stream.md" data-title="modules/chat-stream.md">chat-stream.md</button>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/bolt-diy/repo-docs/modules/provider-model-selection.md" data-title="modules/provider-model-selection.md">provider-model-selection.md</button>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/bolt-diy/repo-docs/modules/chat-api-contract.md" data-title="modules/chat-api-contract.md">chat-api-contract.md</button>
                  <div class="tree-node tree-folder">references/</div>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/bolt-diy/repo-docs/references/source-evidence.md" data-title="references/source-evidence.md">source-evidence.md</button>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/bolt-diy/repo-docs/references/quality-review.md" data-title="references/quality-review.md">quality-review.md</button>
                  <button class="tree-node tree-file" type="button" data-file="case-studies/generated/bolt-diy/repo-docs/glossary.md" data-title="glossary.md">glossary.md</button>
                  <button class="tree-node tree-file" type="button" data-file="case-studies/generated/bolt-diy/repo-docs/change-log.md" data-title="change-log.md">change-log.md</button>
                </div>
              </div>
              <div class="case-file-preview" aria-live="polite">
                <span>walkthroughs/one-real-run.md</span>
                <div class="case-file-content case-markdown-content">Loading generated file...</div>
              </div>
            </div>
          </article>

          <article class="case-repo-tree" id="case-panel-tabby" data-case-panel="tabby" role="tabpanel" aria-labelledby="case-tab-tabby" hidden>
            <div class="case-tree-head">
              <span>TabbyML/tabby</span>
              <strong>repo-docs/ completion service path</strong>
              <a href="case-studies/tabby.md">Open full case</a>
            </div>
            <div class="case-tree-split">
              <div class="case-tree-pane" aria-label="Generated file tree for TabbyML tabby">
                <div class="tree-node tree-root">repo-docs/</div>
                <div class="tree-branch">
                  <button class="tree-node tree-file" type="button" data-file="case-studies/generated/tabby/repo-docs/README.md" data-title="README.md">README.md</button>
                  <div class="tree-node tree-folder">walkthroughs/</div>
                  <button class="tree-node tree-file tree-leaf is-active" type="button" data-file="case-studies/generated/tabby/repo-docs/walkthroughs/one-real-run.md" data-title="walkthroughs/one-real-run.md" aria-current="true">one-real-run.md</button>
                  <button class="tree-node tree-file" type="button" data-file="case-studies/generated/tabby/repo-docs/code-map.md" data-title="code-map.md">code-map.md</button>
                  <div class="tree-node tree-folder">modules/</div>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/tabby/repo-docs/modules/completion-pipeline.md" data-title="modules/completion-pipeline.md">completion-pipeline.md</button>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/tabby/repo-docs/modules/retrieval-context.md" data-title="modules/retrieval-context.md">retrieval-context.md</button>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/tabby/repo-docs/modules/completion-contract.md" data-title="modules/completion-contract.md">completion-contract.md</button>
                  <div class="tree-node tree-folder">references/</div>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/tabby/repo-docs/references/source-evidence.md" data-title="references/source-evidence.md">source-evidence.md</button>
                  <button class="tree-node tree-file tree-leaf" type="button" data-file="case-studies/generated/tabby/repo-docs/references/quality-review.md" data-title="references/quality-review.md">quality-review.md</button>
                  <button class="tree-node tree-file" type="button" data-file="case-studies/generated/tabby/repo-docs/glossary.md" data-title="glossary.md">glossary.md</button>
                  <button class="tree-node tree-file" type="button" data-file="case-studies/generated/tabby/repo-docs/change-log.md" data-title="change-log.md">change-log.md</button>
                </div>
              </div>
              <div class="case-file-preview" aria-live="polite">
                <span>walkthroughs/one-real-run.md</span>
                <div class="case-file-content case-markdown-content">Loading generated file...</div>
              </div>
            </div>
          </article>
        </div>
      </section>

      <section class="section map-section" id="map" aria-labelledby="map-title">
        <div class="section-copy">
          <p class="section-note">Evidence loop</p>
          <h2 id="map-title">Keep the guide close to what the code actually does.</h2>
          <p>
            Start with one behavior you can observe, name the concepts that help explain it, and
            keep the exact source evidence nearby. When the code changes, update the smallest page
            that needs it.
          </p>
        </div>

        <div class="pixel-ledger" aria-label="Repo-Docs map rules">
          <div class="ledger-row" data-step="observe" tabindex="0">
            <strong>Observe</strong>
            <span>Follow a behavior through source, tests, data, or UI.</span>
          </div>
          <div class="ledger-row" data-step="name" tabindex="0">
            <strong>Name</strong>
            <span>Give stable concepts their own small module pages.</span>
          </div>
          <div class="ledger-row" data-step="anchor" tabindex="0">
            <strong>Anchor</strong>
            <span>Keep mechanism details in modules and source evidence in references.</span>
          </div>
          <div class="ledger-row" data-step="repair" tabindex="0">
            <strong>Repair</strong>
            <span>When code changes, update the page that owns that knowledge.</span>
          </div>
        </div>
      </section>

      <section class="section workshop-section" id="artifacts" aria-labelledby="artifacts-title">
        <div class="workshop-copy">
          <p class="section-note">Generated artifacts</p>
          <h2 id="artifacts-title">What Repo-Docs generates</h2>
          <p>
            The output is intentionally small. Instead of one long README, Repo-Docs creates a few
            pages with clear jobs, so reading and lookup both stay manageable.
          </p>
          <div class="inventory-grid" aria-label="Repo-Docs generated artifacts">
            <article class="inventory-card">
              <div class="inventory-meta">
                <h3>Walkthroughs</h3>
                <p>Walk through one behavior from entry point to output.</p>
                <dl class="inventory-stats">
                  <div><dt>Depth</dt><dd>Route</dd></div>
                  <div><dt>Proof</dt><dd>High</dd></div>
                </dl>
              </div>
            </article>
            <article class="inventory-card">
              <div class="inventory-meta">
                <h3>Module pages</h3>
                <p>Explain the concepts and ownership boundaries worth keeping.</p>
                <dl class="inventory-stats">
                  <div><dt>Scope</dt><dd>Concept</dd></div>
                  <div><dt>Drift</dt><dd>Low</dd></div>
                </dl>
              </div>
            </article>
            <article class="inventory-card">
              <div class="inventory-meta">
                <h3>Evidence</h3>
                <p>Keep source evidence, caveats, and quality review easy to check.</p>
                <dl class="inventory-stats">
                  <div><dt>Audit</dt><dd>Source</dd></div>
                  <div><dt>Review</dt><dd>Optional</dd></div>
                </dl>
              </div>
            </article>
            <article class="inventory-card">
              <div class="inventory-meta">
                <h3>Sync rules</h3>
                <p>Tell future agents how to keep the pages current.</p>
                <dl class="inventory-stats">
                  <div><dt>Trigger</dt><dd>Drift</dd></div>
                  <div><dt>Patch</dt><dd>Minimal</dd></div>
                </dl>
              </div>
            </article>
          </div>
        </div>
      </section>

      <section class="section quest-section" id="quests" aria-labelledby="quest-title">
        <div class="quest-heading">
          <p class="section-note">Skill modes</p>
          <h2 id="quest-title">Use the mode that matches where the repo is.</h2>
          <p>
            You can use Repo-Docs when a repo is new, when docs drift, or when a plan needs a
            clearer starting point. In each case, the work starts by checking what is actually true.
          </p>
        </div>

        <div class="quest-advisor" aria-label="Pick your situation">
          <p>What are you trying to do?</p>
          <div class="quest-chips">
            <button type="button" class="is-active" data-quest-pick="build">New repo, no guide yet</button>
            <button type="button" data-quest-pick="sync">Code changed, docs stale</button>
            <button type="button" data-quest-pick="seed">Planning before code exists</button>
            <button type="button" data-quest-pick="refine">Existing guide needs care</button>
          </div>
        </div>

        <div class="quest-board" aria-label="Repo-Docs skill modes">
          <article class="quest-large is-highlighted" data-quest="build">
            <span>Build</span>
            <h3>Start a useful guide for a repo that already exists.</h3>
          </article>
          <article data-quest="sync">
            <span>Sync</span>
            <h3>Refresh the pages affected by code, config, data, or test changes.</h3>
          </article>
          <article data-quest="seed">
            <span>Seed</span>
            <h3>Separate planned work, open questions, and confirmed facts before code exists.</h3>
          </article>
          <article data-quest="refine">
            <span>Refine</span>
            <h3>Improve the guide when a real question shows what readers still need.</h3>
          </article>
        </div>
      </section>

      <section class="section path-section" aria-labelledby="path-title">
        <p class="section-note">Sync loop</p>
        <h2 id="path-title">A practical loop for keeping docs current.</h2>
        <div class="path-track" aria-label="Repo-Docs sync loop">
          <article class="loop-step">
            <strong>Read</strong>
            <p>Open the page that should help answer the question.</p>
          </article>
          <article class="loop-step">
            <strong>Inspect</strong>
            <p>Check the current source, command, artifact, config, or data.</p>
          </article>
          <article class="loop-step">
            <strong>Patch</strong>
            <p>Update the page only when the gap is likely to matter again.</p>
          </article>
          <article class="loop-step">
            <strong>Answer</strong>
            <p>Answer from evidence and leave the repo a little easier to continue.</p>
          </article>
        </div>
      </section>

      <section class="section install-section install-section--cta" id="contribute" aria-labelledby="contribute-title">
        <div class="install-glow" aria-hidden="true"></div>
        <div class="install-copy">
          <p class="section-note">Open source</p>
          <h2 id="contribute-title">Help make Repo-Docs easier to trust and maintain.</h2>
          <p>
            Repo-Docs is open source. If it misses something in a real workflow, issues and PRs are
            welcome. Small fixes, examples, and clearer docs all help.
          </p>
        </div>
        <div class="contribute-panel" aria-label="GitHub contribution links">
          <div class="contribute-panel-head">
            <span>GitHub</span>
            <strong>Open source contribution</strong>
          </div>
          <div class="contribute-actions">
            <a class="contribute-action contribute-action--primary" href="https://github.com/YurunChen/repo-docs-skills/issues">
              <span>GitHub Issues</span>
              <strong>Open issue</strong>
            </a>
            <a class="contribute-action" href="https://github.com/YurunChen/repo-docs-skills/pulls">
              <span>Pull Requests</span>
              <strong>Send PR</strong>
            </a>
          </div>
        </div>
      </section>
    </main>

    <footer class="site-footer">
      <div>
        <a class="footer-brand" href="#top">Repo-Docs</a>
        <p>Keep up with the code your agents write.</p>
      </div>
      <nav class="footer-links" aria-label="Footer">
        <a href="README.md">English README</a>
        <a href="README_CN.md">中文 README</a>
        <a href="../skills/repo-docs/SKILL.md">Skill contract</a>
      </nav>
    </footer>

    <script src="assets/gsap.min.js"></script>
    <script src="assets/site.js?v=20260629-aider-demo1"></script>
  </body>
</html>
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall