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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Kill zombie dev servers and test processes. Use when ports are blocked, processes are hanging, or test runners won't start.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.