my-claude

Review a pull request applying the user's Java, Spock, and architecture preferences on top of standard code review. Use when the user asks to review a PR, review code changes, or mentions "my-review". Also use when the user pastes a GitHub PR URL and asks for feedback.

Read and address review comments on a GitHub pull request. Use when the user asks to address PR comments, handle review feedback, respond to PR reviewers, or mentions "address comments" or "pr comments". Also use when the user has just opened a PR and wants to process incoming review feedback. Works with a PR number/URL argument or auto-detects the PR for the current branch.

Reflect on the current conversation session to extract reusable learnings for CLAUDE.md files and to propose improvements to skills that were actually used or invoked during the session. Use when the user asks to reflect on the session, extract learnings, capture lessons, update CLAUDE.md, improve a skill based on this conversation, or invokes /reflect. Optionally focus on a specific area mentioned by the user.

Use to drive the user's cmux terminal multiplexer — read output from other panes, send input/keys into other terminals, spawn new workspaces/splits/panes, control browser surfaces (Playwright-like), and post desktop notifications. Trigger eagerly whenever the user references work happening in another terminal, pane, workspace, or browser surface ("the other terminal", "my running server", "the pane next to this one", "in my browser", "tell me when X finishes"), or asks Claude to open/split/spawn a terminal or browser. Also trigger when the user says "cmux", "send this to…", "look at what's running in…", "notify me when…", or wants Claude to drive a webpage they have open.

Use when the user asks to implement a feature, add a class or method, fix a bug, refactor code, add test coverage, or run autonomously to drive work forward. Supports explicit phase selection via the first argument (red | green | refactor | forever) and infers the phase from conversation and test state when no phase is given. With no arguments at all, defaults to forever (autonomous loop). Do NOT use for code review, CI/CD setup, testing questions, infrastructure, or documentation tasks.

Resolve security vulnerability Jira tickets (typically SECCOMP-*) by upgrading the indicated package, runtime, or base image everywhere it appears in the repository, then creating a branch, commit, and pull request. Use this skill whenever the user asks to "bump", "fix a vuln", "address a SECCOMP ticket", "upgrade a base image", or mentions a ticket ID that looks like a security remediation — even if they don't explicitly say "bump-fix". Also use when the user pastes a Jira URL to a vulnerability ticket and asks to fix it.

Use when writing, modifying, or reviewing Java code - applies SOLID principles, clean code practices, minimal documentation, and pragmatic abstraction to create maintainable Java applications

Use when user provides Jira issue URLs or mentions Jira tickets - fetches issue details and comments from Jira Cloud using local jira tool, outputs AI-optimized markdown for context gathering

Use when writing or refactoring Spock tests in Java projects - enforces data-driven testing with where blocks, proper mock/stub placement, and descriptive test names following Spock best practices