shouenlee/wiki_architect
plugins/deep-wiki/skills/wiki_architect/SKILL.md
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.
development
Updated Apr 14, 2026
$ install --global
skillsauthnpx skillsauth add shouenlee/ghcp-dev-plugin wiki_architectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 14, 2026, 2:26 AM58.0s2 files scanned
SKILL.md
- name:
- wiki_architect
- description:
- Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.
Wiki Architect
You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.
When to Activate
- User asks to "create a wiki", "document this repo", "generate docs"
- User wants to understand project structure or architecture
- User asks for a table of contents or documentation plan
- User asks for an onboarding guide or "zero to hero" path
Procedure
- Scan the repository file tree and README
- Detect project type, languages, frameworks, architectural patterns, key technologies
- Identify layers: presentation, business logic, data access, infrastructure
- Generate a hierarchical JSON catalogue with:
- Onboarding: Principal-Level Guide, Zero to Hero Guide
- Getting Started: overview, setup, usage, quick reference
- Deep Dive: architecture → subsystems → components → methods
- Cite real files in every section prompt using
file_path:line_number
Onboarding Guide Architecture
The catalogue MUST include an Onboarding section (always first, uncollapsed) containing:
-
Principal-Level Guide — For senior/principal ICs. Dense, opinionated. Includes:
- The ONE core architectural insight with pseudocode in a different language
- System architecture Mermaid diagram, domain model ER diagram
- Design tradeoffs, strategic direction, "where to go deep" reading order
-
Zero-to-Hero Learning Path — For newcomers. Progressive depth:
- Part I: Language/framework/technology foundations with cross-language comparisons
- Part II: This codebase's architecture and domain model
- Part III: Dev setup, testing, codebase navigation, contributing
- Appendices: 40+ term glossary, key file reference
Language Detection
Detect primary language from file extensions and build files, then select a comparison language:
- C#/Java/Go/TypeScript → Python as comparison
- Python → JavaScript as comparison
- Rust → C++ or Go as comparison
Constraints
- Max nesting depth: 4 levels
- Max 8 children per section
- Small repos (≤10 files): Getting Started only (skip Deep Dive, still include onboarding)
- Every prompt must reference specific files
- Derive all titles from actual repository content — never use generic placeholders
Output
JSON code block following the catalogue schema with items[].children[] structure, where each node has title, name, prompt, and children fields.
Example
For a TypeScript REST API project, the output might include: Onboarding (Principal-Level Guide, Zero-to-Hero Guide) → Getting Started (Overview, Setup, Quick Reference) → Deep Dive (API Gateway, Auth Service, Data Layer).
Error Handling
- If the repository has no README, generate catalogue from file structure alone
- If language detection fails, omit comparison language sections
- If repo has fewer than 3 files, produce a minimal single-section catalogue
Related Skills
shouenlee/task_breakdown
tools
VerifiedTrustedCommunity
Decomposes feature descriptions or GitHub issues into ordered subtasks with file-level scope, acceptance criteria, and optional gh issue create. Use when asked to "break down task", "decompose feature", "create subtasks", "plan implementation", "break this into tasks", "task list", or "implementation plan".
SKILL.mdUpdated Apr 14, 2026
shouenlee/release_notes
documentation
VerifiedTrustedCommunity
Generates changelogs from conventional commits, bumps semantic versions in pyproject.toml or package.json, and publishes GitHub releases. Use when asked to "create release", "release notes", "changelog", "bump version", "semantic version", "tag release", "publish release", or "what changed since last release".
SKILL.mdUpdated Apr 14, 2026
shouenlee/python_lint_fix
development
VerifiedTrustedCommunity
Runs ruff, mypy, and bandit on changed Python files — explains violations and auto-fixes with ruff check --fix. Use when asked to "lint", "fix lint", "check types", "type check", "run mypy", "run ruff", "python quality", or "lint python files".
SKILL.mdUpdated Apr 14, 2026
shouenlee/make_skill_template
development
VerifiedTrustedCommunity
Create new Agent Skills for GitHub Copilot from prompts or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional scripts/references/assets folders.
SKILL.mdUpdated Apr 14, 2026