メニュー
Project-aware expert-role for code refactoring. Reads project docs first, enforces TDD, and restructures code to reduce cyclomatic complexity and improve maintainability without altering external behavior.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Language-agnostic endpoint documentation generator. Reads routing and codebase to produce structured API contract documentation for existing endpoints.
Expert-role parity check across project docs, platform instruction surfaces, skills, reusable prompts, workflows, quick-reference material, and implementation evidence when authority depends on the current codebase. Use when checking whether the template system still agrees with itself or when preparing cleanup after major changes.
Project-aware expert-role contract design for APIs, interfaces, repositories, services, message schemas, and module boundaries. Reads project docs first, then produces or reviews a contract consistent with the current repository.
Project-aware expert-role broad verification that reads project docs first, classifies the verification target, and routes to the best specialist skill for executable or non-executable checks across code, contracts, docs, architecture, quality, security, reliability, and project health.
Project-aware expert-role database schema and modeling design. Reads project docs first, then produces a schema design, migration plan, or query optimization strategy consistent with the current repository constraints.
Project-aware expert-role for CI/CD pipeline design and implementation. Reads project docs first, enforces build caching, security gates, test execution, and deployment safety.
| name | refactor |
| description | Project-aware expert-role for code refactoring. Reads project docs first, enforces TDD, and restructures code to reduce cyclomatic complexity and improve maintainability without altering external behavior. |
| argument-hint | Describe the function, file, or module to refactor |
Produces a project-aware, expert-level refactoring plan and execution by reading the repository's project docs first, then applying strict structural improvements.
This skill is reusable across any programming language. It focuses on reducing technical debt, splitting monolithic structures, and improving testability. It should not assume a specific framework or design pattern until the project docs confirm them.
| Document | Why it matters |
|---|---|
docs/project-docs/foundation/architecture.md | Defines the acceptable patterns, boundaries, and coupling rules for the project. |
docs/project-docs/development/testing.md | Defines the required testing frameworks and test coverage expectations. |
docs/project-docs/technical-guidelines/index.md | Provides language-specific linting, style, or idiom rules. |
If the repository lacks the testing docs needed for safe refactoring, call that out and create or update the missing docs instead of refactoring blindly.
Use this skill when tasked with improving existing code without changing its feature set.
| Boundary type | Typical artifacts |
|---|---|
| Function / Method | Reducing cyclomatic complexity, extracting pure functions, eliminating nested conditionals. |
| Class / Module | Applying SOLID principles, injecting dependencies, splitting god classes. |
| File / Directory | Reorganizing imports, breaking large files into logical cohesive units. |
| Naming & Style | Standardizing variable names, updating to project idioms. |
Extract from architecture.md:
Extract from the codebase:
Evaluate the target code for:
Design the new structure:
Ensure all existing comments and docstrings are preserved unless the new structure explicitly invalidates them. In that case, update them accurately.
Use this checklist when reviewing refactored code:
architecture.md respected?When using this skill, the output should include:
@agent use refactor on [Target Function/File] focusing on [Specific Architecture/Simplicity Goal].