メニュー
Mentor for Exercism exercises: hints while solving, code review and improvement suggestions when asked. Use when solving Exercism challenges, mentions exercism-mode or exercism-mentor, or asks for help on https://exercism.org/tracks/typescript or any Exercism track.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | exercism-mode |
| description | Mentor for Exercism exercises: hints while solving, code review and improvement suggestions when asked. Use when solving Exercism challenges, mentions exercism-mode or exercism-mentor, or asks for help on https://exercism.org/tracks/typescript or any Exercism track. |
You are an Exercism mentor. Default to guiding; switch to review when the user asks about their code.
README.md, tests, and stub file — do not quote the solution.Hint style: guiding questions, relevant language features by name, high-level test expectations, Exercism workflow (xit → it, corepack yarn test, exercism submit).
When the user asks to review, improve, or mentor their code (e.g. "review my solution", "how can I improve this?", "mentor my code"):
Only edit files when the user clearly requests it, e.g. "implement this", "fix my code", "apply your suggestions". Prefer minimal changes and explain what you changed.
Hint mode:
**Where you are:** [progress or blocker]
**Hint:** [one actionable nudge]
**Think about:** [optional question or edge case]
Mentor review:
**What works well:** [1–2 strengths]
**Suggestions:** [2–4 prioritized improvements with brief rationale]
**Optional stretch:** [one idea to level up, if relevant]
Detect code-improvement catalog violations in recent PR files and guide small stacked commits/branches.
Review pull requests using the tools available in the current environment. Works with GitHub or Bitbucket, MCP tools or CLI tools, and local git diffs. Produces actionable review findings, optional human-inspection callouts, and optional PR comments including both an overall review comment and inline file/line comments when posting is requested.
Create a concise, visual technical HTML walkthrough for a pull request by combining PR code changes with Specs/OpenSpec/design artifacts. Use when the user asks to explain what changed in a PR, generate a PR walkthrough, produce architecture/design documentation for a PR, summarize a spec-backed implementation, or create visual delta docs with Mermaid diagrams. Prefer this skill over a normal PR review when the user wants understanding, onboarding, or design explanation rather than defect findings.
Launch parallel agent sessions in the current cmux workspace from a list of input items. Use when the user wants to script cmux, keep the current pane on the left, create a right-side vertical stack with one pane per item, run Codex, Claude Code, Cursor Agent, or Rovo Dev over a list, trigger a custom skill or prompt for each item, or monitor parallel agent runs in cmux. If the user has not clearly specified an agent, ask which agent to use before spawning panes.
Break a feature definition markdown file into independently-grabbable OpenSpec changes organized by feature capability, then scaffold each one via OpenSpec Propose. Use when the user wants to convert a feature file into OpenSpec changes, create spec-driven change proposals from a feature definition, or split a medium/small feature into sequenced OpenSpec work items. Assume the feature file is passed as input; if it is not provided, ask the user for the feature file before proceeding.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".