nisavid/mergecraft
Mergecraft: Issue–PR relations, pull-request authoring, publication, Graphite transport, feedback, readiness, merge, and stack repair.
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.
Use when the operator explicitly requests a GitHub branch or PR merge outcome. A merge closeout may invoke the readiness owner as a guarded continuation when repository policy permits; use the readiness skill directly for readiness-only requests. Do not use for description, review, status, check, comment, draft, or publication work without merge.
Use when the operator explicitly asks only to make a pull request ready for review end to end. A merge-owned readiness invocation may call this skill as its delegated readiness leaf; direct callers must still keep readiness separate from review-only, text-only, publish-only, merge, ship, or closeout outcomes.
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.
Use when composing and posting one authorized response to an exact pull request review comment, conversation comment, or submitted-review body, or reconciling that response's uncertain result.
Use when creating a PR with Issue contributions, materially changing either entity's contribution or completion scope, repairing Issue–PR associations, or checking applicable Issue consequences before merge. Skip known dependency-only or mention-only pairs unless correcting an existing association. Skip unrelated comments, labels, formatting, and unchanged relation intent.
Use when standalone GitHub PR creation, canonical title/body/draft-ready publication, an authorized relation-ledger edit on an existing or historical PR, 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.
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.
Use when preparing a narrow stacked PR fixup or follow-up patch whose base is another open PR head.
Use whenever directly drafting, writing, or editing the exact Markdown source of a GitHub Issue or pull-request body, conversation comment, submitted-review body, review-thread root, or review-thread reply, including edits to selected spans of an existing body. For a complete pull-request title and navigable description, use writing-reviewable-pr-descriptions, which consumes this contract. Do not use for repository Markdown files, read-only inspection, posting unchanged text, reactions, thread resolution, review submission, or other GitHub actuation.
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.