Skip to content
TrustedSkillsbeta
Back to all skills

Pre Merge Checklist

Checked
hieutrtr·vlatest·backend

Ensures smooth merges by automatically generating a checklist of required steps and tasks, preventing errors and streamlining collaboration.

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 hieutrtr/ai1-skills --skill pre-merge-checklist -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

hieutrtr

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 hieutrtr/ai1-skills at d8244c1acd.

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

Commit
d8244c1acd
Manifest
skills/pre-merge-checklist/SKILL.md
Scanned
4 files, 738 lines
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 generates a checklist to ensure code changes are ready for merging into a main branch. It helps prevent regressions and ensures quality by prompting for confirmation of common tasks like running tests, updating documentation, and verifying the build process. The generated checklists can be customized based on project needs and team standards.

When to use it

  • Before submitting a pull request or merge request.
  • When onboarding new developers to a codebase.
  • To standardize pre-merge procedures across a development team.
  • For projects with complex deployment pipelines requiring specific verification steps.

Key capabilities

  • Generates customizable checklists.
  • Prompts for confirmation of common tasks.
  • Helps prevent regressions and ensure code quality.
  • Supports standardization of merge processes.

Example prompts

  • "Generate a pre-merge checklist for a Python project."
  • "Create a checklist for merging, including running unit tests and updating the README."
  • "Give me a pre-merge checklist tailored to a React application with Cypress end-to-end tests."

Tips & gotchas

The quality of the checklist depends on the specificity of your prompt. Providing details about the project type or specific concerns will yield more relevant results.