reviewing-documents
Systematic documentation review following document-writer principles. Use when user requests documentation review, quality check, or principle compliance verification.
Découvrez les skills research technical docs, comparez leurs dépôts et consultez leurs instructions.
Systematic documentation review following document-writer principles. Use when user requests documentation review, quality check, or principle compliance verification.
Outline extension implementing protocol for documentation domain
General documentation standards for README, AsciiDoc, and technical documentation with validation, formatting, link verification, and content review workflows
JavaDoc documentation standards including class, method, and code example patterns
JSDoc documentation standards for JavaScript functions, classes, modules, and web components
Creates and updates documentation, adds code comments, writes API documentation
Use to create complete architecture documentation structure. Creates all required architecture documents from templates.
Use to generate development task documents for the Dev agent. Creates specifications describing WHAT needs fixing based on validated issues and investigations.
Generate code using coder agents. Use /code for standard tasks, /code --complex for advanced.
Generates documentation and docstrings for Python code. Use when adding documentation to functions, classes, modules, or creating API documentation.
Use Stig to generate documentation from C/C++ code with Doxygen-style comments
Makeing of README.md files for ROBOLIBS libraries
Conduct structured web research with hypothesis tracking. Synthesizes information from multiple sources into actionable findings. Use for technical research, API docs, best practices. Triggers: web research, lo...
Audit documentation accuracy against code changes. Identifies stale docs, incorrect examples, and missing documentation. Read-only analysis. Use before PR or after implementation. Triggers: review docs, check d...
Generate API documentation in OpenAPI/Swagger, Markdown, or Postman Collection formats. Use when documenting REST APIs, GraphQL schemas, or creating client code examples.
AI 코딩 도우미의 기본 정책을 확인해야 할 때 사용한다. POLICY.md를 기준으로 답변한다.
This skill should be used when the user asks about "codex CLI options", "codex flags", "codex exec command", "codex session management", "codex sandbox modes", or needs reference information about invoking the...
Trigger documentation updates based on recent code changes. Use when user says "update documentation" or "document [scope]". Assesses changes, updates README/feature docs/architecture docs, and verifies documen...
Create epic-specific documentation skill with external reference docs. MUST BE USED for caching external docs. Fetches URLs, caches full content, uses documentation-engineer to generate cohesive summaries, and...
Generate comprehensive documentation for codebases, suitable for both human developers and AI coding assistants. Use when documenting a repository, creating architecture docs, generating API references, writing...
Conduct comprehensive research across the codebase to answer questions, explore solutions, or understand existing implementations. Use when researching a problem, designing a new feature that interfaces with ex...
Generates section list for a page. Deterministic mapping. Does not write content.
Systematically audit documentation against actual codebase to determine accuracy, staleness, and relevance. Use when auditing docs for accuracy, cleaning up stale docs after refactoring, validating docs match i...
Design technical architecture from a PRD. Use when user wants to create an architecture document, define system design, plan technical implementation, or needs to translate product requirements into buildable t...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.