菜单
Use when the user wants to scan compiled Java bytecode (.class / .jar / .war) for bug patterns - null-pointer dereferences, concurrency / multithreading mistakes, performance smells, security flaws, dodgy code, or known-bad API misuse.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when orchestrating broad or multi-issue subagent work where agents, lanes, reviews, or PRs may become too small; use for CuraOS waves, owner-path bundles, local issue queues, many-agent execution, or requests to run more lanes without wasting work in micro PRs.
Use when asked to plan, decide, or execute subagent orchestration: subagents, delegated agents, parallel workers, review agents, multi-source research, broad audits, PR/MR review, worktree-aware execution, model/effort selection, or agent-driven execution.
Use when viewing or printing source/config files to the terminal with syntax highlighting and line numbers - a cat replacement that colorizes code, configs, and diffs. Use bat instead of cat when humans need highlighted file display.
Use when the user wants to format or lint JavaScript, TypeScript, JSX, TSX, JSON, JSONC, CSS, GraphQL, HTML, Vue, Svelte, or Astro - biome is the unified Rust-based replacement for prettier + eslint, doing both with one binary and one config file.
Use when the user formats or lints Dart or Flutter source code from the command line - dart format is the formatter (Black-style, mutates by default) and dart analyze is the static analyzer (errors, warnings, lints). Both ship with the Dart SDK; no separate install.
Use when the user wants a structural, syntax-aware diff between two source files or git revisions - a diff that parses each side as code (Rust, TS, Python, Go, …) and ignores reformatting, brace movement, or whitespace noise. Binary is difft; use for syntax-aware diffs, not plain file viewing.
| name | spotbugs |
| description | Use when the user wants to scan compiled Java bytecode (.class / .jar / .war) for bug patterns - null-pointer dereferences, concurrency / multithreading mistakes, performance smells, security flaws, dodgy code, or known-bad API misuse. |
See references/when-to-use.md. Load only when this section is needed.
See references/invocation.md. Load only when this section is needed.
See references/patterns.md. Load only when this section is needed.
See references/anti-patterns.md. Load only when this section is needed.
See references/cross-refs.md. Load only when this section is needed.
