Reconcile a tracked elixpoo pull request after GitHub reports it merged or closed. Use when Steward Celebrate must validate a terminal fingerprint, update the issue ledger, remove active follow-up memory, retain a bounded completion receipt, and optionally publish a cooldown-controlled safety-gated message.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add elixpo/elixpo_chapter --skill finalize-contribution --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Finalize Contribution?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/elixpo-finalize-contribution)More formats (shields.io, HTML) on the badges page.
---
name: finalize-contribution
description: Reconcile a tracked elixpoo pull request after GitHub reports it merged or closed. Use when Steward Celebrate must validate a terminal fingerprint, update the issue ledger, remove active follow-up memory, retain a bounded completion receipt, and optionally publish a cooldown-controlled safety-gated message.
---
# Finalize a contribution
Use GitHub state as the only terminal authority. Never infer merge or closure from
comments, notifications, branch deletion, or model output.
## Reconcile
1. Load the active follow-up record and require a matching terminal action.
2. Refetch the PR and recompute its outcome fingerprint from the outcome, head SHA,
and GitHub terminal timestamp.
3. Stop if the record is missing, already completed, or the fingerprint changed.
4. Resolve the original issue key from the stored issue URL and update its ledger
status to `merged` or `closed`.
5. Move the PR record from active Gist memory into the bounded completion list.
6. Write a versioned local receipt for workflow and future Project reconciliation.
## Optional public response
- Default to no celebration comment.
- When explicitly enabled, publish one short factual message.
- Pass the complete message through the safety role before posting.
- Do not include token usage, internal state, prompts, or operational metadata.
Keep finalization deterministic and idempotent. Do not call a coding model, mutate
the fork, delete shared repositories, or reopen closed work.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!