メニュー
Use when drafting or editing persisted technical writing artifacts such as commit messages, issue bodies, PR descriptions, documentation comments, or documentation files.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | technical-writing |
| description | Use when drafting or editing persisted technical writing artifacts such as commit messages, issue bodies, PR descriptions, documentation comments, or documentation files. |
Use this skill for persisted technical writing artifacts. Do not apply it to normal chat replies.
Write plans intended for a cheaper or less capable implementation model. Use when the user asks for a plan suitable for another LLM, junior engineer, intern, cheaper model, coding agent, or implementation delegate.
Use when the user asks for ideas, brainstorming, discussion, exploration, possibilities, pros and cons, tradeoffs, or to "think through" something.
Use this skill when asked to plan something, or plan and implement. Do not use when asked to implement a plan.
Use when initializing Rust projects or modifying Cargo.toml, Cargo.lock, cargo config, or other cargo-related files. Prefer this skill for dependency changes, features, package metadata, workspaces, and cargo commands. Do not load it for editing Rust source code generally.
Split an existing commit or PR into smaller reviewable pieces through a one-hunk patch queue. Use when extracting part of a commit, splitting a commit into multiple commits, or splitting PR changes from one or more source commits without starting from direct source edits.
Checkpoint, inspect, and return through session tree branches. Use when exploring uncertain approaches, investigating code, or when the user asks for a forked agent.
