agentsclimarketplace

Git branch review

Skill JasonWarrenUK/goblin-mode/skills/git-branch-review

Three goblins in a trenchcoat pretending to be a senior developer. Claude Code config shaped by ADHD, friction, and spite.

Install
npx -y skills add JasonWarrenUK/goblin-mode --skill git-branch-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

{{ 𝛀𝛀𝛀 }} Assess branch readiness for PR submission

SKILL.md

3.2 KB, 651 tokens by cl100k_base, as published. Nobody here has run it

Assess whether this branch is ready to be submitted as a reviewable pull request.

Analysis Steps

  1. 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.
  2. Identify the base branch (usually main) and list all commits since diverging
  3. 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
  4. 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
  5. 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>
  6. Scan for anti-patterns:
    • Debugging artefacts (console.log, commented-out code)
    • Unresolved conflict markers (<<<<<<<, =======, >>>>>>>)
    • TODO / FIXME comments introduced in this branch
    • Diff size >500 lines (flag for possible split)
  7. 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!: or BREAKING 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.