Skip to content
Back to skills

Merge Prep

ASecurity

Prepare a read-only branch merge analysis with native git merge-tree conflict detection and copy-pasteable manual commands. Use when deciding whether to merge one branch into another. Not for: checkout, merge, rebase, conflict edits, or branch mutation. Output: commits, files, conflicts, evidence, and manual commands.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
ai-agentsgit

Works with

  • terminal

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 24, 2026

npx -y skills add hmj1026/dhpk --skill merge-prep --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Merge Prep?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Merge Prep
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hmj1026-merge-prep/badge)](https://www.skillsdirectory.com/skills/hmj1026-merge-prep)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: merge-prep
description: 'Prepare a read-only branch merge analysis with native git merge-tree conflict detection and copy-pasteable manual commands. Use when deciding whether to merge one branch into another. Not for: checkout, merge, rebase, conflict edits, or branch mutation. Output: commits, files, conflicts, evidence, and manual commands.'
argument-hint: '<source-branch> [--target=<branch>]'
metadata:
  dhpk-invocation-class: implicit-eligible
---

# Merge Prep

## Workflow

Require `<source-branch>` and resolve `--target` to `{TARGET_BRANCH}` or
`main` when omitted. Validate both refs and a clean worktree before analysis.
Use native, read-only Git evidence: merge-base, commit log, changed-file
summary, and `git merge-tree --write-tree <target> <source>` (or report
`UNAVAILABLE` when the installed Git cannot provide that read-only operation).

Report commits, files, conflict details, likely conflict patterns, and
text-only resolution strategies. Emit copy-pasteable commands for a human to
execute later. Never run `git checkout`, `git switch`, `git merge`, `git
rebase`, or a conflict edit. See
[`references/workflow.md`](references/workflow.md) for the exact sequence.

## When NOT to Use

- The worktree is dirty or either branch/ref is missing.
- A merge, checkout, rebase, or conflict resolution should happen now.
- A write-capable branch operation is requested.

## Output

Pre-merge evidence includes source/target refs, merge-base, commits, files,
`merge-tree` output, conflict status, and copy-pasteable manual commands.
Conflicts are findings, not permission to mutate. A complete read-only
analysis ends `PASS` (with its conflict status); missing preconditions or
unexpected Git failures are terminal `BLOCKED`/`FAIL` results. No merge claim
is made.

## Verification

- [ ] Source and target resolve and `git status --porcelain` is empty.
- [ ] Native merge-tree analysis ran without changing the worktree.
- [ ] Commit/file/conflict evidence is included, including clean conflicts
      when none were found.
- [ ] Suggested merge commands are output only and were not executed.

## References

- [`references/workflow.md`](references/workflow.md) — native analysis,
  conflict interpretation, and manual command output.

Files in this skill

  • SKILL.md2.2 KB
  • agents/openai.yaml185 B
  • references/workflow.md1.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.