Documentation Skills

Explain complex or legacy code in plain English, including what it does, why it likely exists, and how it can be safely modified or refactored. Use when users paste confusing, messy, undocumented, or inherited code and ask what it does, how to change it, what might break, or request comments/documentation. Outputs a structured, human-readable breakdown rather than just inline comments

Document how data flows through a feature or system from user action to API to state to UI — producing a step-by-step trace and Mermaid diagram. Use whenever a user wants to map, trace, or document data movement - "how does X work end-to-end", "document this feature", "trace what happens when a user does Y", or when they share code and ask how it works.

Design and document a complete Git workflow for a team, including branching strategy, commit conventions, pull request process, merge rules, CI requirements, and release strategy. Use when creating Git workflow docs, CONTRIBUTING guidelines, or defining version control processes for a project.

Generate a clear, structured PR description from a diff, commit list, branch name, or change summary. Use when users want to write or improve a pull request description, fill a PR template, or document code changes for review. Includes what changed, why, testing steps, risks, and follow-ups.

Generate a structured, professional README.md from a project's files, such as file structure, manifests (e.g., package.json), and entry points. Use when users want to create or improve a README, document a project, or explain a codebase. Includes project purpose, tech stack, setup, usage, API/CLI reference, environment variables, folder structure, and contribution guidelines.

Generate structured REST API documentation for a set of endpoints. Use when users want API reference docs, endpoint documentation, or descriptions of HTTP routes. Trigger when endpoints, route definitions, controller code, or HTTP methods like GET, POST, PUT, PATCH, or DELETE are provided.

Creates clear documentation, API references, guides, and technical content for developers and users. Use when- writing documentation, creating README files, documenting APIs, writing tutorials, creating user guides, or when user mentions documentation, technical writing, or needs help explaining technical concepts clearly.

Write a comprehensive test plan for a feature or system. Use when users want to create a test plan, QA strategy, or testing checklist for a feature, bug fix, API, UI component, or release. Trigger when a feature, spec, PRD, or ticket is shared and the user asks what or how to test.