Skip to content
TrustedSkillsbeta
Back to all skills

Review Merge Readiness

Checked
heyvhuang·vlatest·backend·MIT

Analyzes code review feedback, identifies merge conflicts, and flags pull requests as ready for merging.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add heyvhuang/ship-faster --skill review-merge-readiness -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

heyvhuang

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned heyvhuang/ship-faster at 64047d24e0.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
64047d24e0
Manifest
skills/review-merge-readiness/SKILL.md
Scanned
4 files, 332 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to automatically assess whether a code merge is ready for deployment. It analyzes pull requests to identify potential issues, ensuring that only high-quality changes are integrated into the main branch.

When to use it

  • Before initiating a merge request in your CI/CD pipeline.
  • To prevent broken builds caused by untested or incomplete code changes.
  • During code reviews to provide an automated second opinion on logic and style.
  • When enforcing strict quality gates before production releases.

Key capabilities

  • Automatically scans pull requests for readiness criteria.
  • Identifies potential bugs, missing tests, or integration risks.
  • Provides actionable feedback to developers before merging occurs.
  • Integrates seamlessly into existing workflow tools.

Example prompts

  • "Review the latest pull request and tell me if it's ready to merge."
  • "Check this code change for any obvious bugs or missing test cases."
  • "Is the current branch stable enough for a production deployment?"

Tips & gotchas

Ensure your repository has sufficient commit history and test coverage data for accurate analysis. This skill works best when combined with other automated testing tools to cover edge cases it might miss.