agentsclimarketplace

Llm wiki repo docs

Skill po4yka/llm-wiki-skills/skills/llm-wiki-repo-docs

Portable Agent Skills for building, operating, evaluating, and governing LLM-Wiki knowledge systems.

Install
npx -y skills add po4yka/llm-wiki-skills --skill llm-wiki-repo-docs

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Build or maintain an LLM-Wiki for codebase documentation. Use when the user wants agent-readable repo docs, architecture maps, module pages, ADR links, OpenWiki-style output, or AGENTS.md/CLAUDE.md pointer patterns for Claude Code, Codex, Cursor, or other coding agents.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.0 KB, 577 tokens by cl100k_base, as published. Nobody here has run it

LLM-Wiki Repo Docs

Goal

Create or improve a repository LLM-Wiki that helps coding agents understand and modify the codebase safely.

When to use

  • The user asks for an LLM-Wiki, agent-readable repo docs, or architecture maps for a codebase.
  • Setting up or refreshing AGENTS.md/CLAUDE.md pointer patterns for Claude Code, Codex, Cursor, or similar coding agents.
  • Module/package maps or ADR links have gone stale after a major refactor and need a maintenance pass.
  • Preparing OpenWiki-style repo documentation for a team repo where changes should land via PR.

Inputs

  • Repository path.
  • Existing docs, README, ADRs, package manifests and project instructions.
  • Target agent(s).
  • Desired mode: plan, apply, or PR-ready changes.

Procedure

1. Inspect repository shape

Identify:

  • languages and package managers;
  • major modules/services/packages;
  • tests and build commands;
  • existing docs and ADRs;
  • current AGENTS.md/CLAUDE.md;
  • generated docs folders that should not be edited.

2. Choose output location

Use one of:

wiki/          general LLM-Wiki docs
openwiki/      OpenWiki-style repo docs
_docs/wiki/    if project docs live under docs

Do not mix repo docs with personal second-brain material.

3. Generate repo wiki map

Create or update pages for:

  • architecture overview;
  • module/package index;
  • data flow;
  • build/test/deploy map;
  • common change workflows;
  • conventions and gotchas;
  • ADR/decision history;
  • agent entrypoints.

4. Use pointer pattern

Keep AGENTS.md/CLAUDE.md short. Add pointers to wiki pages instead of embedding large docs.

Example:

For architecture and module maps, read `wiki/index.md` first.

5. Add maintenance loop

Recommend:

  • wiki-lint after major refactors;
  • scheduled docs health check;
  • PR-based documentation updates;
  • CODEOWNERS for important domains;
  • stale markers for generated architecture pages.

Output

## Repo docs summary

## Pages created or proposed

## Instruction-file updates

## Architecture gaps

## Maintenance plan

## Next skill

Safety gates

  • Do not claim code behavior without checking source files.
  • Do not overwrite hand-written ADRs.
  • Do not put secrets or internal URLs in broadly readable docs.
  • Do not generate direct commits to team repos when PR workflow is expected.
  • Re-verify architecture and module descriptions against current source files before publishing pages, since generated maps drift quickly after refactors.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.