writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization | 新しいスキルの作成、既存スキルの編集、またはデプロイ前にスキルが機能するか検証する際に使用 - プロセスドキュメントにTDDを適用し、記述前にサブエージェントでテストし、合理化に対して堅牢になるまで反復
terraform-test
Comprehensive guide for writing and running Terraform tests. Use when creating test files (.tftest.hcl), writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking providers and data sources, testing module outputs and resource configurations, or troubleshooting Terraform test syntax and execution. Terraform test is typically used when validating Terraform modules.
terraform-test
Comprehensive guide for writing and running Terraform tests. Use when creating test files (.tftest.hcl), writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking providers and data sources, testing module outputs and resource configurations, or troubleshooting Terraform test syntax and execution.
doc-reviewer
Reviews documentation for completeness, accuracy, and consistency with the project's DX_GUIDE.md standards. Validates documentation structure, checks for broken links, ensures examples are up-to-date, and verifies technical accuracy. Use when creating or updating documentation, reviewing doc-heavy PRs, or ensuring doc quality.
markdownlint-writer
Write or edit Markdown files while conforming to markdownlint rules used in this repo.
pre-commit-review
ADVISORY validation of code against design principles that linters cannot enforce. Loaded by go-code-reviewer agent for design analysis guidance. Also invoked by @refactoring (after pattern application). Can be manually invoked for standalone code review. Categorizes findings as Design Debt, Readability Debt, or Polish Opportunities. Does NOT block commits.
fix-line-endings-check-bash
Fix line endings AND check bash syntax in one step (recommended). Use after creating or editing bash scripts.
frontend-quality-bar
Enforce a high-quality, production-ready standard for changes in this Next.js + Chakra UI frontend repo. Use for UX polish, accessibility, performance, error/loading states, code hygiene, and “ready to merge” checks (lint/format/build).
code-review
Review code changes and remove AI-generated patterns like excessive comments, gratuitous defensive checks, type escape hatches, and over-engineering.
code-reviewer
Reviews PHP/CakePHP code for quality, standards compliance, and best practices
receiving-code-review
Verification-first approach to code review feedback. Use when receiving review comments during the implement phase. Evaluate suggestions rigorously before implementing - no performative agreement.
boy-scout-rule
Always leave code better than you found it. Use this when encountering any code quality issues, even if unrelated to your current task.
code-style-checker
Checks python code for use of print statements and suggests using logging instead. Use this when the user asks to review code or check for bad practices.
project-validator
Validate project structure, dependencies, and configuration files. Use when setting up projects, checking project health, or troubleshooting configuration issues.
rust-style-conventions
Foundational Rust style conventions that apply universally to all Rust code. Covers import organization, naming conventions, and code formatting standards. This skill is automatically applied to all Rust implementations and should be referenced by all other Rust skills.
validation
This skill should be used when the user asks to "validate requirements", "review requirements quality", "check requirements completeness", "verify traceability", "check INVEST compliance", "validate user stories", "requirements health check", "quality gate check", or when running /re:review validation.
applying-sun-lab-style
Applies Sun Lab Python coding conventions when writing, reviewing, or refactoring code. Covers .py files, docstrings, type annotations, naming conventions, README.md files, git commit messages, and Claude skill files. Use when writing new code, modifying existing code, reviewing pull requests, creating documentation, writing commit messages, or when the user asks about coding standards.
reviewing-code
Code review methodology for evaluating implementation changes. Use when reviewing code changes for quality, design, correctness, and maintainability. Focuses on changes made during implementation using Conventional Comments for clear, actionable feedback.
code-review
Use after completing tasks to review code for quality and spec compliance. Two-stage review: Spec Compliance first, then Code Quality.
