Menu
Format, lint, test, and commit changes. Detects repo tooling automatically.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Build, serve, and watch a morph page, a single .jsx file previewed locally with hot reload whose state lives in the file itself (useMorph) and which can run approved shell commands (useShell). Serving always includes watching the output, since the reader's clicks and comments come back through the file for you to act on. Use whenever you author, serve, or respond to a morph document.
Review uncommitted changes for issues, missed items, and improvements. Use after finishing a substantial change, before committing, or when the user asks to check the work.
Read and control tmux panes from inside a tmux session - see what other panes show, send commands to them, create splits, run long-lived processes. ALWAYS use when asked about another pane, before running any tmux command, or when a command needs a real TTY or would outlive the shell tool timeout.
| name | git-commit |
| description | Format, lint, test, and commit changes. Detects repo tooling automatically. |
| argument-hint | ["message"] |
| allowed-tools | Bash(git *), Read, Glob, Grep |
| disable-model-invocation | true |
Commit all changes in the repo with proper formatting, linting, and testing.
Check what tooling exists:
!ls -la package.json Makefile Cargo.toml pyproject.toml go.mod 2>/dev/null || true
!cat package.json 2>/dev/null | head -50 || true
Study the repo's commit message style:
!git log --oneline -20 2>/dev/null || true
Note the pattern: conventional commits? imperative mood? lowercase? prefix? scope? Look at casing, punctuation, length, and structure. Your commit message MUST follow this pattern.
!git status
!git diff --no-ext-diff
!git diff --cached --no-ext-diff
Based on what you found:
package.json, Cargo.toml, go.mod, pyproject.toml), reconcile its lockfile so it is not left behind - npm install --package-lock-only (or pnpm install --lockfile-only / yarn install --mode update-lockfile), cargo generate-lockfile, go mod tidy, etc. Stage the refreshed lockfile in the same commit as the manifest change. This is what stops a later install from dirtying the tree.git add the relevant files by path (never git add -A - avoid staging .env, credentials, or large binaries) and commit with a message matching the repo's style. Go from most independent change to most dependent.If $ARGUMENTS is provided, use it as the commit message for a single commit of all changes. Otherwise, generate messages matching the repo's commit style, splitting into multiple commits when it matches the repo's pattern.
Fix any formatting/lint issues automatically. If tests fail, report and stop. After the final commit, run git status - the tree must be clean; if a sync or build step left changes behind, fold them into the relevant commit before finishing.