Analyze, plan, rebuild, refresh, validate, or improve repository wiki documentation through /home/almaz/TOOLS/repo-wiki-cli-skill when the user wants a reusable .repowiki structure, reference pack extraction, selective regeneration, hook-based freshness, or temp-clone validation on real repositories.
Use this skill as a thin wrapper over /home/almaz/TOOLS/repo-wiki-cli-skill.
The runtime is the source of truth for:
.repowiki/ or legacy .qoder/repowiki/ tree;.repowiki/<language>/content/ scaffold generation for new repositories;hook-run;.repowiki/<language>/meta/repo-wiki-cli/;Use this skill when the user wants any of the following:
.repowiki/ for a project;analyze on the target repository.rebuild and write into .repowiki/.install-hook or hook-run..repowiki/ as the skill-owned output root..qoder/repowiki/ as legacy read input when present.ru unless the user explicitly asks for another language.PYTHONPATH=/home/almaz/TOOLS/repo-wiki-cli-skill/src python3.11 -m repo_wiki_cli_skill.cli ... when using the runtime directly.rebuild before testing hook-run on a repo that has no .repowiki/ yet./tmp/ and keep the loop local to the temp clone.self-improve when the task is to stress the runtime itself; use manual temp-clone loops when reviewing actual generated pages is important.analyze inspects current RepoWiki state.extract-reference emits a normalized reference pack.plan emits the planned universal RepoWiki structure.rebuild writes .repowiki/.refresh-check computes impacted pages for the latest commit.install-hook installs the managed post-commit refresh hook.hook-run executes one refresh pass and writes freshness artifacts.self-improve runs a non-interactive improvement loop on copied repositories..repowiki/<language>/content/*.md.repowiki/<language>/meta/repowiki-metadata.json.repowiki/<language>/meta/repo-wiki-cli/freshness-ledger.json.repowiki/<language>/meta/repo-wiki-cli/latest-refresh-report.json.repowiki/<language>/meta/repo-wiki-cli/refresh-summary.md