jasonwarrenuk/Branch: Review
skills/git-branch-review/SKILL.md
{{ 𝛀𝛀𝛀 }} Assess branch readiness for PR submission
$ install --global
skillsauthnpx skillsauth add jasonwarrenuk/goblin-mode Branch: 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: Jul 18, 2026, 7:17 AM163.4s1 file scanned
SKILL.md
- name:
- Branch: Review
- description:
- {{ 𝛀𝛀𝛀 }} Assess branch readiness for PR submission
- when_to_use:
- Before opening a PR, when you want a readiness verdict on commit quality, diff size, and branch naming grounded in exact git facts rather than a skim.
- model:
- opus
- disable-model-invocation:
- true
- allowed-tools:
- ["Read", "Glob", "Grep", "Bash(git:*)", "Bash(~/.claude/library/scripts/branch-facts.sh:*)"]
Assess whether this branch is ready to be submitted as a reviewable pull request.
Analysis Steps
- Gather the exact numbers first:
"$HOME"/.claude/library/scripts/branch-facts.sh [base]emits JSON (ahead/behind, conventional-commit and branch-name compliance, WIP commits, diff size, conflict markers, TODOs and console.logs added, test files touched, svu bump). Judge from these facts; the steps below are the judgement layer, not fact-gathering to repeat by hand. - Identify the base branch (usually
main) and list all commits since diverging - Review the full diff for:
- Incomplete work (half-implemented features, placeholder logic)
- Obvious bugs or unhandled edge cases
- Code quality issues that would block a reviewer
- Check commit history:
- Conventional commit compliance (
type(scope): description) - Logical atomicity — each commit should represent one coherent change
- No WIP, fixup, or junk commits that should have been cleaned up
- Conventional commit compliance (
- Check branch name against naming conventions:
- Format:
<prefix>/<short-description>(lowercase, hyphens, imperative) - Valid prefixes:
feat,fix,enhance,refactor,types,perf,styles,layout,docs,test,deps,config,build,agents,chore,ci,deploy,spike,experiment,wip,hotfix - Breaking change branches should use
<prefix>/breaking-<description>
- Format:
- Scan for anti-patterns:
- Debugging artefacts (
console.log, commented-out code) - Unresolved conflict markers (
<<<<<<<,=======,>>>>>>>) TODO/FIXMEcomments introduced in this branch- Diff size >500 lines (flag for possible split)
- Debugging artefacts (
- Detect breaking changes:
- Removed or renamed exports, functions, types, or components
- Changed function signatures (required parameters added/reordered)
- Modified return types in a widening direction
- Database schema changes (columns removed/renamed, constraints changed)
- HTTP API changes (routes, methods, request/response shapes)
- New required environment variables
- Changed component props (removed, renamed, type-changed, newly required)
Output Format
Verdict
One of: Ready | Needs Work | Blocked
Branch Health
- Branch name compliance
- Commit message quality
- Commit atomicity
Code Quality Flags
Specific issues found, with file and line references where possible. Omit this section if none found.
Breaking Changes
Any detected breaking changes with context. Flag format:
⚠️ Breaking change — consider
feat!:orBREAKING CHANGE:footer
Omit this section if none found.
Recommended Next Steps
Ordered list — blockers first, then improvements, then nice-to-haves.
If the verdict is Ready, offer to run /git:pull-request immediately.
Related Skills
jasonwarrenuk/Roadmap: Build Zip
tools
VerifiedTrustedCommunity
{{ 𝚫𝚫𝚫 }} Rebuild roadmap-system.zip, the distributable snapshot of the roadmap tooling (scripts, HTML template, conventions reference, and every roadmap-touching skill, including this one).
5SKILL.mdUpdated Jul 21, 2026
jasonwarrenuk/skills/task-suggest
tools
VerifiedTrustedCommunity
--- name: "Suggest: Task" description: "{{ 𝚫𝚫𝚫 }} Suggest the next logical task — grounded in the roadmap's pre-vetted ready-set when one exists, codebase analysis otherwise" when_to_use: "When you don't know what to work on next and want a grounded recommendation rather than picking arbitrarily." model: haiku effort: low disable-model-invocation: true allowed-tools: ["Read", "Glob", "Grep", "Bash(python3:*)", "Bash(npm:*)", "Bash(bun:*)", "Bash(pnpm:*)", "Bash(deno:*)"] argument-hint: [named
5SKILL.mdUpdated Jul 17, 2026
jasonwarrenuk/Roadmap: Migrate
development
VerifiedTrustedCommunity
{{ 𝛀𝛀𝛀 }} Convert an old simple-style roadmap (single Markdown, four statuses, <a name> anchors, roadmaps.json pointer registry) into the rich phase-array format (roadmaps.json source of truth + PHASE task list + prose overview).
5SKILL.mdUpdated Jul 17, 2026
jasonwarrenuk/PR: Create
data-ai
VerifiedTrustedCommunity
{{ ƔƔƔ }} Create a pull request to main — wordy or shiny (with screenshots), ready-for-review or draft
5SKILL.mdUpdated Jul 17, 2026