repo-wiki
Repo Wiki
Overview
Create and maintain a structured knowledge base from the codebase. Primary goal: help LLMs and coding agents work faster, with less searching, less repeated explanation, and better architectural grounding. Output should work as lightweight context engine: concise enough to scan, specific enough to act on, and kept in sync as repository changes.
This skill is for LLM-facing internal engineering knowledge such as architecture notes, module pages, PRD-style specs, integration maps, and change-aware wiki upkeep. Human readability matters, but agent efficiency comes first. It is not for public marketing docs or end-user documentation.
When to Use
- Generate an initial wiki for a repository, package, service, or app
- Refresh docs after a PR, commit, refactor, migration, or incident fix
- Create or maintain architecture notes, module pages, feature specs, and PRD-style docs
- Delete stale knowledge when code, routes, jobs, packages, or configs disappear
- Prepare better navigation context, retrieval context, and decision context for coding agents and LLMs
More from bohdan-shulha/skills
qt-qml-attachments
>-
17commit-jira
Create and execute Git commits with a required JIRA-style subject and required body. Use when the user asks to commit changes, write commit messages, or prepare a clean commit and expects a ticket-prefixed subject. Always run a pre-commit safety guard first, abort on log files or untracked high-risk binary extensions, then stage with `git add . -A`.
10claude-cli-agent-protocol
>-
10commit
Create and execute Git commits in Conventional Commits format with a required body. Use when the user asks to commit changes, write commit messages, or prepare a clean commit. Always run a pre-commit safety guard first, abort on log files or untracked high-risk binary extensions, then stage with `git add . -A`.
9plan-b
Create a concise plan for coding/build tasks, especially when users say "I want to make..." or "I need to do...". Use to generate a final plan by aggregating multiple subagent plan variants, include ASCII diagrams/flows/UI mockups when possible, and follow the create-plan style (read-only scan, minimal questions).
8