Loading...
Loading...
Found 13 Skills
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
Use this skill to create CodeTour .tour files — persona-targeted, step-by-step walkthroughs that link to real files and line numbers. Trigger for: "create a tour", "make a code tour", "generate a tour", "onboarding tour", "tour for this PR", "tour for this bug", "RCA tour", "architecture tour", "explain how X works", "vibe check", "PR review tour", "contributor guide", "help someone ramp up", or any request for a structured walkthrough through code. Supports 20 developer personas (new joiner, bug fixer, architect, PR reviewer, vibecoder, security reviewer, and more), all CodeTour step types (file/line, selection, pattern, uri, commands, view), and tour-level fields (ref, isPrimary, nextTour). Works with any repository in any language.
Write or revise AGENTS.md per embedded output contract. Use when creating Agent entry for new projects, auditing existing AGENTS.md, or adopting the AI Cortex entry format.
Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans .github/copilot directory files and copilot-instructions.md to extract project information, technology stack, architecture, development workflow, coding standards, and testing approaches while generating well-structured markdown documentation with proper formatting, cross-references, and developer-focused content.
Generate project-level AGENTS.md guides that capture conventions, workflows, and required follow-up tasks. Use when a repository needs clear agent onboarding covering structure, tooling, testing, task flow, README expectations, and conventional commit summaries.
Bootstrap a Memory Bank for a new or existing repository, then route into PRD-driven or brownfield workflows.
Update repo documentation and agent-facing guidance such as AGENTS.md, README.md, docs/, specs, plans, and runbooks. Use when code, skill, or infrastructure changes risk doc drift or when documentation needs cleanup or restructuring. Do not use for code review, runtime verification, or `agent-readiness` setup.
DISTILL
Research a specific system and create or update its blueprints/ documentation
Create, optimize, update, and validate AGENTS.md files with maximum token efficiency. Use when the user asks to (1) create new AGENTS.md files for any repository, (2) optimize/condense existing AGENTS.md to reduce token count, (3) update/refresh AGENTS.md to sync with codebase changes, (4) validate AGENTS.md quality and completeness, or (5) improve AGENTS.md files to be more effective for AI agents. Always generates token-efficient, condensed output focused on actionable commands and patterns while maintaining model-agnostic language.
Create or update repository README.md files with concise, human-skimmable structure and verified metadata. Use when writing or refreshing README content, adding or correcting badges, documenting stack and deployment/services, and explicitly reporting testing coverage (unit, integration, e2e api, e2e web) plus CI execution status.
Create and improve README documents for GitHub projects. Use when the user wants to write a new README, improve an existing one, audit README quality, or asks about documentation best practices for their repository.