java-code-reviewer

Review Java backend projects, pull requests, diffs, and snippets for production-risk bugs in Spring Boot, Spring Cloud, MyBatis, MyBatis-Plus, Redis, Kafka, Reactor, WebFlux, transactions, concurrency, security, performance, DDD, and microservice architecture — focusing on capital-loss, data-corruption, authorization-bypass, and incident-causing defects. Use for transaction integrity, Spring proxy correctness, MyBatis wrapper safety, Redis/Kafka duplicate consumption, and incident-blocking PR review. Do NOT use for: code style, formatting, naming, lint, or other non-incident review.

跳到安装查看文件

仓库: liyown/superpower-enterprise
最近来源活动: 2026年6月10日 03:35
检测到的 SKILL.md 语言: 英语
星标: 1
分支: 0

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 AI 助手安装

复制这段 Prompt，发给你正在使用的 AI 助手。

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/liyown/superpower-enterprise/tree/main/skills/java-code-reviewer.

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/liyown/superpower-enterprise --skill java-code-reviewer

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

19 个文件

SKILL.md

来源说明 · 只读预览

name: java-code-reviewer
description: Review Java backend projects, pull requests, diffs, and snippets for production-risk bugs in Spring Boot, Spring Cloud, MyBatis, MyBatis-Plus, Redis, Kafka, Reactor, WebFlux, transactions, concurrency, security, performance, DDD, and microservice architecture — focusing on capital-loss, data-corruption, authorization-bypass, and incident-causing defects. Use for transaction integrity, Spring proxy correctness, MyBatis wrapper safety, Redis/Kafka duplicate consumption, and incident-blocking PR review. Do NOT use for: code style, formatting, naming, lint, or other non-incident review.

# Java Code Reviewer Review Java backend code for real production risk. Keep the entrypoint small and load scenario prompts only when the code needs them. ## Required Loading Always load `prompts/reviewer.md`. Load additional prompts only when relevant: - `prompts/spring-reviewer.md`: Spring Boot, Spring Cloud, transactions, proxy annotations, validation, async, scheduling. - `prompts/mybatis-reviewer.md`: MyBatis, MyBatis-Plus, SQL, Wrapper, batch operations, indexes, tenant filters. - `prompts/security-reviewer.md`: authorization, tenant isolation, injection, sensitive data, file/URL/deserialization risks. - `prompts/concurrency-reviewer.md`: idempotency, duplicate writes, locks, thread pools, ThreadLocal, cache races. - `prompts/reactor-reviewer.md`: Reactor/WebFlux blocking, subscribe, timeout, retry, backpressure, EventLoop misuse. - `prompts/redis-kafka-reviewer.md`: Redis cache failure modes, Kafka consumption, ordering, offset, retries, compensation. ## Review Contract - Find concrete bugs, not generic advice. - Bind every finding to code evidence and an execution path. - Mark uncertain findings as `需要结合上下文确认`. - Do not output style comments unless they hide a real defect. - If no clear high-risk issue is found, output exactly: ```text 未发现明确高风险问题。 ``` Use the severity and output contract from `prompts/reviewer.md`. ## Examples Each bad example has a matching `good-<file>` in this same `examples/` directory that shows the minimal fix for every Critical/High finding. Read both side by side when triaging a real diff.

在 GitHub 查看

返回搜索返回安装

data-lineage-trace

Use when you need to prove where a piece of data (PII, PHI, payment data, customer identifier) originates, where it flows through the system, where it lands, and who reads it. Triggers on: data lineage, PII flow, GDPR right-to-erasure, data residency, schema change, retention policy, 'where does field X come from', 'who reads PII column Y', 'walk this field end to end', deletion propagation, audit trail, data classification. Do NOT use for: static code review (use java-code-reviewer, react-code-reviewer, go-code-reviewer, python-code-reviewer, or node-code-reviewer for that), or for design-time brainstorming (use obra/superpowers brainstorming). Complementary to goal-driven-development, which orchestrates the spec-to-code flow; data-lineage-trace is the regulated-data counterpart that runs after a change lands.

2026-06-10

goal-driven-development

Use this skill to orchestrate an existing goal or spec through the dev flow. Load when the user asks for end-to-end feature execution, a goal-to-PR pipeline, or any task that crosses spec → implementation → review → knowledge capture. The skill is a thin router: it names the 6 phases (spec intake, blast-radius check, implementation, verification, review gate, knowledge capture) and the skill that does the work for each phase. Do NOT use for: a single review (load the matching `*-code-reviewer` directly), or for a generic author-craft task like TDD / debugging / brainstorming (use obra/superpowers). Complementary to the 17 enterprise-flow skills; for the planned v0.6.1+ skills, the orchestrator names which of them does the work for each phase.

2026-06-10

enterprise-stack

Use when an agent needs the full enterprise-dev-flow skill set: language-specific code review (java/react/go/python/node), spec-to-code orchestration (goal-driven-development), durable post-impl knowledge (project-knowledge-capture), doc drift linting (spec-doc-linter), and (planned) data lineage / CODEOWNERS / incident trace / compliance / rollout / RFC / observability skills. Triggers on: 'set up enterprise skills', 'install the full stack', 'enterprise-stack', 'give me the augment', 'what skills should I load', 'superpower-enterprise'. Do NOT use for: a single review (load the matching `*-code-reviewer` directly); a generic TDD/debugging/brainstorming request (use obra/superpowers).

2026-06-10

查看这个仓库的全部 Skills

java-code-reviewer

来源信息

安装方式

用 AI 助手安装

检查来源文件

同仓库更多 Skills

用 AI 助手安装

同仓库更多 Skills