メニュー
Read this skill before making git commits
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Find deepening opportunities in a codebase, informed by CONTEXT.md and docs/adr/. Records findings in Solo scratchpads and can turn selected refactors into Solo todos. Use when improving architecture, finding refactoring opportunities, or making a codebase more testable and AI-navigable.
Solo-native planning workflow. Use when asked to "plan", "brainstorm", "design", "create a plan", "I want to build", or "let's build". Covers both orchestrating a plan (scout → planner → workers → review) and acting as the interactive planner subagent.
Review code changes for quality, security, and correctness. Use when asked to "review", "code review", "check my changes", or when acting as a reviewer subagent. Produces a structured review with prioritized findings, saved to a Solo scratchpad when one is provided.
Fast codebase reconnaissance — map existing code, conventions, and patterns for a task. Use when asked to "scout", "explore the codebase for", or when acting as a scout subagent gathering context for a planner or worker.
Implement one Solo todo — write code, verify it, commit with the commit skill, save a result note, and close the todo. Use when acting as a worker subagent executing a single well-scoped Solo todo.
Write clear Solo todos that workers can execute without losing architectural intent. Use when asked to "create todos", "write todos", "break into tasks", "plan todos", or create work items from a plan. Ensures each todo has outcomes, examples, constraints, and verification criteria.
SOC 職業分類に基づく
| name | commit |
| description | Read this skill before making git commits |
Create a git commit for the current changes using Conventional Commits format with a polished, highly descriptive message. If there are commit hooks - do not skip them, it's your responsability to leave things better than they were.
<type>(<scope>): <summary>
type REQUIRED. Use feat for new features, fix for bug fixes. Other common types: docs, refactor, chore, test, perf.scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, parser, ui).summary REQUIRED. Short, imperative, <= 72 chars, no trailing period.git log should understand the change without looking at the diff.Signed-off-by).git status and git diff to understand the current changes (limit to argument-specified files if provided).git log -n 50 --pretty=format:%s to see commonly used scopes.git commit -m "<subject>" (and -m "<body>" if needed).