code-reviewer
Reviews code for style, bugs, and best practices. Use when asked to review or analyze code quality.
Discover research technical docs skills, compare source repositories and read the instructions for each workflow.
Reviews code for style, bugs, and best practices. Use when asked to review or analyze code quality.
Understand exactly and surgically the user's request by following this skill. Use it when you have doubts about how to implement features, and need some clarification from the user.
Research best practices, guides, and libraries. Use when needing documentation, recommendations, implementation guidance, or library comparisons.
Search technical documentation using executable scripts to detect query type, fetch from llms.txt sources (context7.com), and analyze results. Use when user needs: (1) Topic-specific documentation (features/com...
코드 작성이 필요할 때 coder-agent 활용 가이드. 직접 코드 작성 대신 위임
Generate a complete software specification document for the current project/repo, including architecture, data model, key processes, pseudocode, and Mermaid diagrams (context, container/deployment, module relat...
Retrieve authoritative library documentation and code examples.
Writes explanatory comments to code to improve readability for developers and AI systems. Use when documenting code or improving code comprehension.
Explains code in simple terms with visual diagrams. Use when the user asks to explain code, understand how something works, or wants a code walkthrough.
Format documentation with emojis, status bars, and versioning matrix. Use when creating or updating README files, documentation, specs, or any markdown files.
Write self-documenting code with minimal, helpful comments that explain large sections of logic without cluttering the codebase. Use this skill when writing code comments, documenting complex logic, reviewing w...
Generate hardware setup and wiring instructions for IC10 code. Use when user wants to know how to physically connect devices to use their IC10 scripts.
Perform a repo-wide, evidence-based audit of documentation against the current codebase and recent changes. Produces a proposed, fully rewritten documentation set in TempDoc-ForUserReview and asks for approval...
Create, update, and maintain clear, accurate, and well-organized technical documentation for complex codebases. This agent focuses on understanding the current state of the code and existing documentation befor...
Guide interactive research and POC creation to understand features deeply. This skill should be used when planning to implement a new feature and needing to research design patterns, understand integration poin...
Provides API design patterns for Rust backends including request validation with validator, OpenAPI documentation with utoipa, and SwaggerUI integration. Use when building REST APIs with Axum, adding request va...
Creates comprehensive GitHub project documentation including README, CONTRIBUTING, CODE_OF_CONDUCT, CHANGELOG, architecture docs, and API documentation. Analyzes codebase to generate accurate, well-styled docum...
Generate package-info.java files for Java packages. Use when the user requests to add package documentation files to Java packages, create package-info.java files, or document Java package structures. Automatic...
Auto-activating documentation cache with fresh API docs. Fetches and automatically consults cached documentation when user works with libraries/frameworks.
Write purposeful code comments that explain the "why" behind technical decisions, complex logic, and non-obvious implementations using JSDoc for components and APIs. Use this skill when documenting component pr...
Knowledge retrieval from multiple sources. Search docs, web, and code with intelligent routing.
Document user-facing features in a codebase. Use when asked to document features, explain what software does, or generate feature docs. Identifies features (not technical layers), then produces numbered markdow...
Generate Japanese documentation from spec files. Use AUTOMATICALLY after writing or editing any file matching specs/**/*.md (excluding specs/**/docs/*). Also use when user says "generate spec docs", "spec docs"...
Generate a specification file from user input/requirements. Use when user says "generate spec", "create spec", "write spec", "spec from requirements", or provides feature requirements and asks to create a spec....
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.