bash · Found in 2 repositories

check-merge

Check once whether the branch's merge target (the branch its PR is based on) advanced or the PR landed since the branch was last attested, then hand any advance back to the enclosing flow to decide. While the PR is open, also reconcile the `Proposed squash body:` comment `/finalize` left on it, and the PR title it lands under — editing both in place when the branch has drifted from them. A manual one-shot — run it when you return to a session whose branch is attested to see if the merge targe...

Install

Install with the skills CLI. It asks which coding agents to install into:

npx skills add 'vzakharov/muthur/.claude/skills/check-merge/SKILL.md#main'

Or install globally for one agent:

# Claude Code → ~/.claude/skills/
npx skills add 'vzakharov/muthur/.claude/skills/check-merge/SKILL.md#main' -g -a claude-code
# Codex → ~/.agents/skills/
npx skills add 'vzakharov/muthur/.claude/skills/check-merge/SKILL.md#main' -g -a codex
# Cursor → ~/.cursor/skills/
npx skills add 'vzakharov/muthur/.claude/skills/check-merge/SKILL.md#main' -g -a cursor

Manual install locations: Claude Code ~/.claude/skills/, Codex ~/.agents/skills/, Cursor ~/.cursor/skills/. Source-path status is inferred from metadata; it does not verify a live download. Scan and quality scores describe registry checks and are not a guarantee of safety.

What the registry checked

Scanned 2026-11-16 by registry scanner 1.1.7 (ruleset 371c677df515, content 8e244dd12f2f).

  • File size limit
  • Frontmatter and schema
  • Dangerous code patterns
  • Sensitive file paths
  • Bundled scripts and support files
  • Blocked source repositories
  • Prompt injection phrases
  • Hardcoded credentials
  • Obfuscated execution chains

Findings: 1 warning: schema validation (1).

Checks are pattern-based and cover the archived copy; they do not guarantee the skill is safe.

Content history

  1. 2026-11-16 Matches the author's file; frontmatter is not installablesha256:7f4ab8793922 · 1 file

Each entry is a period in which the archived files (SHA-256 per file) and their match against the author's repository stayed the same. Upstream checks run at most weekly, so detection can lag.

Attribution and permissions

Check the original repository for permission and license terms before reuse. Registry metadata does not grant a license.

This guide links to the author’s instructions and includes metadata only.

Request removal or correct attribution

For the skill author

Add this badge to your README to link readers to the registry home:

Listed on Claude Skills Registry

[![Listed on Claude Skills Registry](https://majiayu000.github.io/claude-skill-registry/assets/listed-badge.svg)](https://majiayu000.github.io/claude-skill-registry/)

Copies with matching content

Exact Markdown body copies across 2 repositories. This count does not identify the original author.

More in bash