ask-matt
無料Ask which skill or flow fits your situation. A router over the skills in this repo.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to resolve an in-progress git merge/rebase conflict.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Repository configuration overrides this skill's default planning paths.
If a Planning root is defined, resolve CONTEXT.md, docs/adr/,
docs/agents/, .scratch/, and .out-of-scope/ from that root.
Skill-local paths remain unchanged.
See the current state of the merge/rebase. Check git history, and the conflicting files.
Find the primary sources for each conflict. Understand deeply why each change was made, and what the original intent was. Read the commit messages, check the PRs, check original issues/tickets.
Resolve each hunk. Preserve both intents where possible. Where incompatible, pick the one matching the merge's stated goal and note the trade-off. Do not invent new behaviour. Always resolve; never --abort.
Discover the project's automated checks and run them — typically typecheck, then tests, then format. Fix anything the merge broke.
Finish the merge/rebase. Stage everything and commit. If rebasing, continue the rebase process until all commits are rebased.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Ask which skill or flow fits your situation. A router over the skills in this repo.
日本語の概要は準備中です。原文の説明を表示しています。
Re-explain the previous assistant message in a much simpler way — for when the reply made you go 'bro what'. Use /bro to get a plain-language version of the last answer.
日本語の概要は準備中です。原文の説明を表示しています。
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
日本語の概要は準備中です。原文の説明を表示しています。
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
日本語の概要は準備中です。原文の説明を表示しています。
Drive one ticketed effort through parallel implementation, independent review, serial integration, and one open pull request.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
日本語の概要は準備中です。原文の説明を表示しています。