メニュー
Set up pre-commit hooks for the current repo. Use when user wants to add pre-commit hooks, configure commit-time linting, formatting, type checking, or testing. Triggers on "pre-commit", "git hooks", "linting hooks", or /setup-pre-commit.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Draft Outlook or Teams messages in Charles's voice using the My Brain /write communication rules. Trigger when Charles invokes /write, mentions /write, or asks for this vault workflow by name.
Design and ship a new core hook in this repo (claude-workflow) — fetch the exact event schema, write a stdlib-only fail-open script, TDD it against real subprocess+git behavior, wire it into every affected preset, and push to both GitHub and GitLab. Use when adding a new Claude Code hook (Stop, SubagentStop, ConfigChange, SessionStart, etc.) under core/hooks/.
Run Charles's My Brain /context-then-delegate workflow to resolve real-world ambiguity (email/SharePoint/Slack) before writing a coding-agent prompt. Trigger when Charles invokes /context-then-delegate, mentions /context-then-delegate, or is about to write a delegated prompt for a task with unresolved domain ambiguity.
Run Charles's My Brain /clickup-task-sync workflow to sync vault action items into ClickUp without duplicating tasks. Trigger when Charles invokes /clickup-task-sync, mentions /clickup-task-sync, or asks to sync action items / a 1:1 recap into ClickUp.
Run Charles's My Brain /fix-issue workflow to resolve a filed issue under TDD + mutation-teeth-check + review-before-commit discipline. Trigger when Charles invokes /fix-issue, mentions /fix-issue, or asks to fix/resolve a specific filed issue with test rigor.
Run Charles's My Brain /mr-review-packet workflow to generate a self-guided reviewer packet for a large merge request. Trigger when Charles invokes /mr-review-packet, mentions /mr-review-packet, or asks for a review packet / reviewer walkthrough for a big MR.
| name | setup-pre-commit |
| description | Set up pre-commit hooks for the current repo. Use when user wants to add pre-commit hooks, configure commit-time linting, formatting, type checking, or testing. Triggers on "pre-commit", "git hooks", "linting hooks", or /setup-pre-commit. |
Before proceeding, verify:
.git/ directory. If not found, inform the user and stop.uv --version to confirm uv is availablenpx --version to confirm npx is availableIf prerequisites fail, inform the user what's missing and how to install it.
Check the project root for:
| Signal | Result |
|---|---|
pyproject.toml present, no package.json | Python → read python-setup.md |
package.json present, no pyproject.toml | JS/TS → read js-setup.md |
| Both present | Ask user (see below) |
| Neither present | Inform user: no supported project detected, stop |
Use AskUserQuestion to offer three options:
python-setup.mdjs-setup.mdpython-setup.md including the "Both-Languages Mode" sectionDelegate to the language-specific setup file. Each file presents available checks via AskUserQuestion.
If the user selects no checks: inform them that no hooks will be installed and exit gracefully.
Follow the language-specific setup file.
Follow the language-specific setup file to create config file(s) based on user selections.
Follow the language-specific setup file to activate hooks in git.
Run hooks against the full codebase to confirm they work.
ruff --fix, ruff format, prettier --write) and re-run.Stage and commit all created/modified config files.