⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

pre-merge-checklist

@autohandai⭐ 0 stars

Runs a pre-merge checklist on the current branch, covering a clean build, passing tests and linters, a scoped diff, no secrets or debug code, migrations, config and docs, and a clear description, then reports pass, fail or not applicable for each item with evidence. Use before opening or merging a pull request, when asked whether a branch is ready to merge, or as a final gate after a review.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐ 0 on GitHubGitHub ↗

New / niche

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

Code review skills

Three skills for checking a branch before it merges. A diff reviewer reports findings by severity with file:line, a checklist runs your own build and test commands, and a test gap finder lists changed behaviour that no test checks. They work in any language, since they only rely on git and the commands your project already has.

Install

From the root of your repo:

git clone https://github.com/autohandai/skillpack-code-review
mkdir -p .claude/skills
cp -R skillpack-code-review/skills/* .claude/skills/

Copy the skill folders themselves, so you get .claude/skills/diff-review/SKILL.md and not a nested pack folder. Some agents only look one level deep. These work well as personal skills too, in ~/.claude/skills/.

Ask for a review and most agents will pick the right skill. To call one by name, mention it: $diff-review in Autohand Code, or /diff-review in Claude Code. For example: "$diff-review against develop".

Skills

SkillWhat it does
diff-reviewReads git diff against the base branch and reports blocker, major, minor and nit findings, each with file:line and a fix
pre-merge-checklistRuns build, tests, lint, secret and debug searches, and migration and config checks, then reports pass, fail or not run
test-gap-finderMaps each changed branch to the test that would catch it breaking, and suggests the missing ones

Adapting it

  • Change the base branch default (main) if yours is different.
  • Add your team's own rules to the "look for these" list in diff-review, such as logging conventions or banned APIs.
  • Add items from your PR template to pre-merge-checklist.
  • Adjust the test path patterns in test-gap-finder to your layout.

Keep the name in the frontmatter the same as the folder name.

If a check gives you noise, please open an issue with an example.

Runs in Autohand Code (free CLI, any model): https://autohand.ai/cli/?utm_source=skillpack-code-review&utm_medium=github

Until 31 October 2026: first month of Pro for $10 with code FOUNDING10 (first-time customers).

MIT licensed. See LICENSE.

// HOW IT'S BUILT

KEY FILES

skills/pre-merge-checklist/SKILL.mdREADME.md

// REPO STATS

0 stars