Run linters and formatters to fix code style issues. Use when cleaning up style violations, formatting code, or after implementation to ensure code meets project standards.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Run the full linting and formatting suite for the detected project type(s).
Run these commands based on project type. All detected languages run for polyglot projects.
# Python linting (if pyproject.toml or requirements.txt exists)
([ -f pyproject.toml ] || [ -f requirements.txt ]) && {
# Ruff - fix code quality issues
ruff check --fix . 2>&1 || true
# Ruff - format all files
ruff format . 2>&1 || true
# mypy - type check
mypy . 2>&1 || true
}
# JS/TS linting (if package.json exists)
[ -f package.json ] && {
# ESLint - use lint:eslint if exists (projects with existing linter), else lint
if grep -q '"lint:eslint"' package.json 2> /dev/null; then
bun run lint:eslint 2>&1 || true
else
bun run lint 2>&1 || true
fi
# Prettier - format all files
bun run format --if-present 2>&1 || true
# TypeScript type check (if tsconfig.json exists)
[ -f tsconfig.json ] && bunx tsc --noEmit 2>&1 || true
}
# Go linting (if go.mod exists)
[ -f go.mod ] && {
# golangci-lint - fix and report issues
golangci-lint run --fix ./... 2>&1 || true
# golangci-lint - format
golangci-lint fmt ./... 2>&1 || true
}
After running, report:
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Run comprehensive code audit for architecture, dead code, and test quality. Use when reviewing overall codebase health, checking for architectural violations, or before marking a feature complete.
日本語の概要は準備中です。原文の説明を表示しています。
Behavior-first feature development — use when building new capabilities, continuing feature work, or when work introduces new state or multiple user flows. Discovers desired behavior through examples and scenarios before implementation. Do NOT use for bug fixes, typos, or small isolated changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to explore options, weigh approaches, or think through uncertainty before committing to a direction. Collaborative brainstorming and rubber ducking — divergence-first thinking partner.
日本語の概要は準備中です。原文の説明を表示しています。
Kill zombie dev servers and test processes. Use when ports are blocked, processes are hanging, or test runners won't start.
日本語の概要は準備中です。原文の説明を表示しています。
Root cause debugging before fixes. Use when investigating bugs, diagnosing test failures, troubleshooting unexpected behavior, or when previous fix attempts failed. Enforces investigate-first discipline.
日本語の概要は準備中です。原文の説明を表示しています。
Extract tacit knowledge through non-obvious microquestions — things only the user knows that can't be found in code, docs, or research. Use when you're about to guess at intent, context, or constraints during SAFEWORD's understanding flow. Also use when user says 'ask me', 'what do you need to know', or when another skill (bdd, brainstorm, debug) needs user context before proceeding. Do NOT use for questions answerable by reading the codebase or searching the web.
日本語の概要は準備中です。原文の説明を表示しています。