---
title: "mergecraft"
description: "Mergecraft: Issue: PR relations, pull-request authoring, publication, Graphite transport, feedback, readiness, merge, and stack repair."
canonical: https://agentpluginsdirectory.com/plugins/mergecraft--nisavid
last-updated: 2026-10-21
---

# mergecraft
Mergecraft: Issue: PR relations, pull-request authoring, publication, Graphite transport, feedback, readiness, merge, and stack repair.
- Slug: mergecraft--nisavid
- Publisher: Ivan D Vasin
- Repository: https://github.com/nisavid/provingkit
- Manifest: plugins/mergecraft/plugin.json
- Version: 1.0.0
- License: MIT
- Category (editorial): integrations
- Skills: 11 (addressing-pr-review-feedback, getting-prs-merged, getting-prs-ready-for-review, graphite, interacting-with-pr-review-feedback, maintaining-issue-pr-relations, publishing-reviewable-prs, resuming-reviewed-prs, stacking-pr-fixups, writing-github-issue-and-pr-markdown, writing-reviewable-pr-descriptions)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-09-01
- Repository last pushed: 2026-10-21
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/mergecraft--nisavid
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What mergecraft does, in the publisher's words

Mergecraft is an Agent Plugins pull-request lifecycle package with a native Claude adapter. It owns reviewer navigation, guarded PR publication, Graphite draft transport, feedback coordination and interaction, review readiness, merge closeout, and stacked fixups. topology.json is the only machine-readable graph and operation-ownership authority. Its schema_version versions Mergecraft's local topology shape, not a repository-wide interchange schema.

Canonical PR publication requires every caller to select required or explicit not-required review. Required mode fail-closes through the authenticated installed Task Witness front door and accepts only a current, trust-anchored, bare-clean Tricritical terminal projection bound to the exact publication candidate. Receipts retain only redacted digests and distinguish witnessed required publication, explicit not-required publication, legacy v2 records, and unwitnessed reconciliation. This release proves required-review success only with repository fixtures; its new-publication Tricritical producer chain is not live-reachable. Required live publication remains intentionally unavailable until that chain is installed and registered.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/nisavid/provingkit/HEAD/plugins/mergecraft/README.md

## Skills

- addressing-pr-review-feedback: Use when a caller needs a complete read-only GitHub review-feedback snapshot for orientation, or an author needs to adjudicate and address requested changes, unresolved threads, or stale review comments.
- getting-prs-merged: Use when the operator explicitly requests a GitHub branch or PR merge outcome, and only for that terminal outcome. Do not use for description, review, status, check, comment, readiness, draft, or publication work without merge.
- getting-prs-ready-for-review: Use when the operator explicitly asks only to make a pull request ready for review end to end. Do not use for review-only, text-only, publish-only, merge, ship, or closeout requests, including composite requests that also mention readiness; getting-prs-merged owns those terminal outcomes.
- graphite: Use when working with Graphite `gt` stacks: creating or tracking stacked branches, navigating or reparenting a stack, restacking, submitting or updating stacked PRs, fixing Graphite metadata, or diagnosing stack ancestry and publication state.
- interacting-with-pr-review-feedback: Use when posting an evidence-backed reply or reaction to pull request feedback, or when resolving an authorized GitHub review thread.
- maintaining-issue-pr-relations
- publishing-reviewable-prs: Use when standalone GitHub PR creation, canonical title/body/draft-ready publication, publication-evidence audit, or evidence reconciliation is required, including fork-sync and fixup PRs. Do not use for generic PR inspection, comments, checks, threads, or merge actuation.
- resuming-reviewed-prs: Use when returning to a stale, neglected, conflicted, CI-blocked, or otherwise long-running reviewed pull request and needing to recover its exact target, local checkout, authority, and next lifecycle owner.
- stacking-pr-fixups: Use when preparing a narrow stacked PR fixup or follow-up patch whose base is another open PR head.
- writing-github-issue-and-pr-markdown
- writing-reviewable-pr-descriptions: Use when creating or changing a GitHub PR title and/or body, including draft, stacked or Graphite, publication, summary, media, diagram/atlas, access-note, caveat, or preservation-sensitive work. Do not use for read-only inspection, comments, checks, threads, or merge-only work with unchanged text.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.