devoxx/review
.claude/skills/review/SKILL.md
Review local code changes for bugs, regressions, missing tests, and pragmatic improvements. Use when the user asks to review the current changes from `git status`, or to review a specific backlog task by id such as `task-65` or `TASK-65`. Also trigger when the user says things like "review", "review current changes", "check my changes", "look over the diff", or "review task-42".
$ install --global
skillsauthnpx skillsauth add devoxx/devoxxgenieideaplugin reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 5:25 PM5.7s1 file scanned
SKILL.md
- name:
- review
- description:
- Review local code changes for bugs, regressions, missing tests, and pragmatic improvements. Use when the user asks to review the current changes from `git status`, or to review a specific backlog task by id such as `task-65` or `TASK-65`. Also trigger when the user says things like "review", "review current changes", "check my changes", "look over the diff", or "review task-42".
Review
Overview
Review the current local changes or the implementation tied to a backlog task id and report concrete findings, not a changelog. Treat this as a code review unless the user explicitly asks for edits.
Workflow
-
Resolve the review target. If the prompt includes a backlog task id, locate the task markdown in
backlog/tasks/first, thenbacklog/completed/if needed. Read the description, acceptance criteria, and referenced files. If no task id is given, start fromgit status --shortand review the current local changes directly. -
Build review scope from local context. Check
git status --short, inspect the diff for files related to the task, and read surrounding code where behavior is affected. Preferrgand targetedgit diff -- <path>over broad scans. -
Review for defects and regressions. Prioritize:
- broken behavior versus the task intent
- stale callers or UI paths left behind after refactors
- contract mismatches across main/preload/renderer/shared code
- silent failure handling and misleading fallback behavior
- missing or weak tests for the changed behavior
- unnecessary performance regressions or duplicate work
- Verify when useful. Run focused tests for the touched area if they are available and cheap. Mention clearly when verification is blocked or when broader typecheck/test failures are unrelated.
Output
Report findings first, ordered by severity. For each finding:
- state the severity
- describe the bug/risk or improvement
- include clickable file references with line numbers when available
- explain the user-visible or maintenance impact briefly
After findings, include:
- open questions or assumptions if any
- a brief note on verification performed
If no findings are discovered, say that explicitly and mention residual risk or missing coverage.
Prompt Shape
Interpret prompts like review, review current changes, or review the changes from git status as a request to review the current working tree. Interpret prompts like task-56, review task-56, or review task-56 and report any issues/bugs or possible improvements as a review of the local changes associated with that task.
Related Skills
devoxx/start-task
tools
VerifiedTrustedCommunity
Create a feature branch for a backlog task, switch to it, and start implementation. Use when the user says "start task-123", "work on task-123", "implement task-123", or invokes /start-task with a task ID.
637SKILL.mdUpdated Apr 15, 2026
devoxx/.claude/skills/release
tools
VerifiedTrustedCommunity
# Release Workflow 1. ASK the user for the target version number - do not assume 2. Update version in: build.gradle.kts, plugin.xml, application.properties, and any other version files 3. Skip local config files (e.g., local.properties) 4. Update plugin change-notes in plugin.xml with new version section 5. If CHANGELOG.md exists at the project root, add a new version section at the top with categorized entries (Added, Changed, Fixed, Documentation, Dependencies) based on merged PRs/commits sinc
637SKILL.mdUpdated Apr 15, 2026
devoxx/.claude/skills/pr
development
VerifiedTrustedCommunity
# Create PR Workflow 1. Ensure all changes are on a feature/fix branch (create one if on main/develop) 2. Run the build: `./gradlew build` 3. Run tests: `./gradlew test` 4. If build+tests pass, commit with a conventional commit message 5. Push the branch 6. Create a PR with a descriptive title and body summarizing changes 7. Report the PR URL
637SKILL.mdUpdated Apr 15, 2026
devoxx/git-commit-push-pr
development
VerifiedTrustedCommunity
Commit all changes, push to remote, and open a pull request in one go. Use when the user says "commit push pr", "ship it", "open a pr", or invokes /git-commit-push-pr.
637SKILL.mdUpdated Apr 15, 2026