style-guide
Coding style guidelines for NixOS, Neovim, and Git. Use when writing or formatting Nix code, Neovim config, or working with Git workflow.
Coding style guidelines for NixOS, Neovim, and Git. Use when writing or formatting Nix code, Neovim config, or working with Git workflow.
A comprehensive guide and set of instructions for performing code reviews on the codebase.
Submit code review requests to multiple AI providers (GitHub Copilot, Anthropic Claude, OpenAI Codex, Google Gemini) and get patches back. Use when user says "code review", "review this code", "get a patch for", or needs AI-generated unified diffs for code fixes.
Use when a mechanical code change needs review before applying. Delegates grunt work to local LLMs — saves cloud tokens. Generates patch for review. Use for changes that might need adjustment. Files must be <500 lines.
Reviews code for style, bugs, and best practices. Use when asked to review or analyze code quality.
When reviewing coding test solutions. This Skill reviews coding test solutions and provides feedback. it adds an evaluation section to the README.md file in the problem-solving folder, including areas for improvement, strengths, and other application ideas based on the provided template. Use this skill when user requests "코테 리뷰", "풀이 리뷰", "리뷰 작성", "리뷰를 작성해줘", "코드 리뷰", or any similar coding test review request.
This skill should be used when the user asks to "review code", "check quality", "assess implementation", "validate standards", "identify issues", or requests code review and quality assessment. Use for systematic code review, quality checks, and best practices validation. Do NOT use for writing code or making design decisions.
Write, debug, review and explain source code following object-oriented best practices, DDD principles, and comprehensive testing standards. Use when writing new code, refactoring, debugging, code review, or explaining programming concepts.
Use for code review and quality feedback from Codex. Triggers on "codex review code", "codex code review", "have codex review this", "get codex feedback on code".
Enhanced docs linting with AI-powered features. Enhanced with Context7 MCP for up-to-date documentation.
Generate accessibility fixes for identified issues using MCP servers for component patterns (magentaa11y-mcp), ARIA guidance (aria-mcp), WCAG criteria (wcag-mcp), and user impact (a11y-personas-mcp). Use this skill when you have a list of accessibility issues and need to produce corrected code with full context. Part of the a11y-orchestrator workflow.
코드 문서화 전문 skill. 주석 작성, 인라인 주석 추가, 문서화 품질 검토를 수행합니다. 사용 시기: (1) 코드에 주석 추가 요청 시 (2) 문서화 품질 검토 요청 시 (3) "문서화", "docs", "주석 추가" 키워드 사용 시 (4) 새 API endpoint 작성 후 (project)
Write self-documenting code with minimal, helpful comments that explain complex logic without documenting temporary changes or fixes. Use this skill when adding comments to code, documenting functions or classes, or explaining complex algorithms. When writing or editing any code file that may benefit from explanatory comments. When reviewing existing comments to ensure they remain evergreen and relevant. When deciding whether code needs comments or if better naming and structure would be clearer. This skill applies to all code files in any programming language including `.js`, `.ts`, `.py`, `.rb`, `.java`, `.go`, `.php`, and others.
OpenAI Codex CLIを使用してコードレビューを実行する。Claude CodeからCodexにレビューを依頼したい時に使用。トリガー:「Codexにレビュー」「codexでコードレビュー」「差分をCodexでチェック」「Codexにコードを見てもらう」「レビューをCodexに依頼」
Write self-documenting code with minimal, helpful comments that explain logic rather than changes. Use this skill when adding comments to TypeScript files, writing JSDoc documentation, deciding whether code needs commenting, or reviewing existing comments. Apply when writing n8n node code, helper functions, or any code where you need to balance clarity with comment density.
Maintain documentation freshness and code-doc alignment. Use when detecting stale documentation, suggesting doc updates during implementation, validating doc accuracy, or generating missing documentation. Handles staleness detection, coverage analysis, and doc/code synchronization.
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
Writes explanatory comments to code to improve readability for developers and AI systems. Use when documenting code or improving code comprehension.
根据 leaf Spec 或 design.md 自动生成代码。当用户说"生成代码"、"实现功能"、"写代码"时自动触发。支持 CAF v0.6.5 直接从 Spec 生成。
Add detailed comments explaining WHY code works, its context, edge cases, and performance implications. Use when user mentions "add comments", "document", "explain code", "improve readability", or "maintainability". Supports C++, Python, Java, JavaScript, Go, Rust, SQL.
Comprehensive Python programming guidelines based on Google's Python Style Guide. Use when Claude needs to write Python code, review Python code for style issues, refactor Python code, or provide Python programming guidance. Covers language rules (imports, exceptions, type annotations), style rules (naming conventions, formatting, docstrings), and best practices for clean, maintainable Python code.
Generate hierarchical code maps from any codebase for AI agent consumption. Use when: (1) Analyzing or understanding a codebase structure, (2) Creating documentation of code architecture, (3) Mapping dependencies between files, (4) Extracting class hierarchies and call graphs, (5) Onboarding to a new project, (6) Preparing context for AI-assisted code modifications. Supports Python, JavaScript, TypeScript, Go, Rust, Java, C/C++, Ruby, PHP, and 20+ languages via tree-sitter.
Detects code/documentation drift, validates examples, generates diagrams, auto-updates documentation