repo-wiki

Name: repo-wiki
Availability: InStock
Author: Almaz

Analyze, generate, and refresh universal .repowiki scaffolds across repositories.

Updated Mar 25, 2026

Search Tags:#automation #cli #structure #wiki #freshness #repo-wiki #reference-pack

Ready to run

npx skills add https://github.com/almazom/agents_slash_skills --skill repo-wiki

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-wiki
Source: https://github.com/almazom/agents_slash_skills/tree/main/repo-wiki
Command: npx skills add https://github.com/almazom/agents_slash_skills --skill repo-wiki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a thin wrapper to manage universal RepoWiki structures across repositories, enabling generation, regeneration, and validation of .repowiki content, including reference pack extraction and freshness tracking.

Core Features & Use Cases

Thin wrapper over repo-wiki-cli-skill to analyze, rebuild, refresh, and validate universal .repowiki structures.
Generate universal .repowiki scaffolds (.repowiki/language/content, meta) for new projects and maintain references packs.
Hook-based freshness and temp-clone validation on real repositories.

Quick Start

Run the repo-wiki skill on a target repository to analyze, generate, or refresh its universal .repowiki scaffold.

Frequently Asked Questions about repo-wiki

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate consistent wiki documentation scaffolds across multiple repositories?▼

RepoWiki generation creates universal .repowiki scaffolds, including content, meta, and reference packs, to establish consistent documentation structures across repositories. It converts existing wiki content or legacy formats into a language-scoped, reusable scaffold.

What is the best way to track documentation freshness on temporary repository clones?▼

Freshness tracking on temporary clones validates documentation currency by applying hook-based validation during repository analysis. This ensures universal .repowiki structures remain up-to-date and accurately reflect the current codebase state.

How do I convert legacy wiki content into a reusable language-scoped scaffold?▼

Converting legacy wiki content uses the analyze and extract-reference commands to transform existing formats into language-scoped, reusable .repowiki scaffolds. This process supports frontmatter-driven entry points and optional resource directories.

Can I orchestrate documentation rebuilds and validation through a CLI runtime?▼

A CLI runtime orchestrates analyze, rebuild, hook-run, and extract-reference commands to manage universal .repowiki structures. This allows automated regeneration and validation of documentation scaffolds directly from the command line.

Does RepoWiki validation support frontmatter-driven entry points and resource directories?▼

RepoWiki validation explicitly satisfies frontmatter-driven entry points and optional resource directories within the generated .repowiki scaffold. This ensures structural consistency and proper metadata alignment across refreshed documentation.

When should I refresh universal RepoWiki structures instead of manually editing documentation?▼

Refreshing RepoWiki structures is necessary when converting legacy formats, ensuring freshness across temporary clones, or rebuilding scaffolds after structural changes. It automates validation and reference pack extraction to maintain consistency without manual edits.