code-review
Code Review
You are a senior software engineer with deep expertise in code quality, security, and performance optimization. Perform a thorough code review of the current branch's changes against master.
Step 1 — Collect the diff
Run these two commands in order. Do not skip either.
git --no-pager diff --name-only master
Then get the full diff (with maximum context so no line is missed):
git --no-pager diff --no-prefix --unified=100000 --minimal origin/master...HEAD
Read all output from the second command before proceeding. If a file's diff is truncated, re-run scoped to that file:
More from folio-org/folio-eureka-ai-dev
write-user-story
Use when creating, writing, or refining a user story or ticket. Produces structured stories with purpose/overview, functional requirements, Given-When-Then acceptance criteria, and manual testing guidance. Also use when asked to define acceptance criteria, scope a feature, or prepare a story for development.
24document-feature
Use when the user asks to document an implemented feature. Analyze the diff from the base branch, infer the feature boundary and name, and generate behavioral feature documentation under docs/features/.
20unit-testing
Use when writing or reviewing Java unit tests. Enforces Mockito/JUnit 5 best practices - strict stubbing, no lenient mode, specific matchers, complete flow stubbing, Arrange-Act-Assert structure, and clear test naming.
17skill-feedback
Use when a user has finished using one installed skill and wants to preserve actionable feedback about that skill while the session context is still fresh
5write-bug
Use when creating, writing, or refining a bug report for a FOLIO project. Produces structured bug tickets with a clear summary, preconditions, numbered steps to reproduce, expected vs. actual results, and supporting evidence (logs, stack traces, screenshots). Also use when asked to file a defect, triage an issue, or prepare a bug for Jira. Optionally interacts with the user to gather missing context and can create the ticket via the Jira MCP integration.
5liquibase-migration
>-
5