github-issue-closeout-race-safe
Close GitHub issues without losing the evidence comment when multiple agents or races may close the issue concurrently.
Best use case
github-issue-closeout-race-safe is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Close GitHub issues without losing the evidence comment when multiple agents or races may close the issue concurrently.
Teams using github-issue-closeout-race-safe should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/github-issue-closeout-race-safe/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How github-issue-closeout-race-safe Compares
| Feature / Agent | github-issue-closeout-race-safe | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Close GitHub issues without losing the evidence comment when multiple agents or races may close the issue concurrently.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# GitHub issue closeout race-safe pattern Use when: - closing issues after verification or implementation - multiple agents/terminals may act on the same issue - the closeout comment is important evidence and must not be lost ## Problem `gh issue close --comment "..."` is convenient, but in live multi-agent use the comment can be lost if the issue becomes closed before the command lands cleanly. ## Safe pattern 1. Post the evidence comment first. 2. Close the issue as a separate command. ```bash gh issue comment <issue> --body-file /tmp/closeout.md gh issue close <issue> ``` ## Why this works - The closeout evidence becomes durable even if a separate process closes the issue moments later. - It avoids silent loss of the most important verification/implementation summary. ## Recommended closeout block Include: - Result: landed / already done / blocked - Evidence checked - Validation commands/results - Commit hashes or artifact paths - Residual risks or blockers ## Extra verification After commenting/closing, verify: ```bash gh issue view <issue> --json state,comments,url ``` Confirm: - issue state is `CLOSED` when intended - the closeout comment is present in recent comments ## When not necessary If you intentionally want a single quick close with no meaningful evidence, `gh issue close` alone is fine. But when evidence matters, always comment first, then close.
Related Skills
marine-safety-incidents
Collect, analyze, and report marine safety incident data from 7 global maritime authorities. Use for incident scraping, safety trend analysis, risk assessment, geographic hotspot identification, and marine safety reporting.
flywheel-closeout
Use this at the end of substantial repo or agent waves to convert evidence-backed lessons into proposed durable assets: skills, scripts, rules/checks, prompt templates, docs, or issues. Always use it when the user mentions flywheel, wave closeout, repo ecosystem learning, durable asset promotion, or learning-to-tools.
plan-gated-issue-execution-wave
Execute a multi-issue architecture/planning wave in a plan-gated repo, then safely transition approved issues into implementation with file-based Codex prompts, local approval markers, subprocess monitoring, and cleanup handling for sandbox/hook edge cases.
tax-filing-session-setup-with-github-tracking
Structured workflow for preparing and tracking a tax filing session using prepared documents, task checklist, and GitHub issue cross-referencing
tax-filing-session-setup-with-github-traceability
Structured workflow for setting up a multi-file tax filing session with GitHub issue tracking and prepared-file validation
staged-issue-tree-creation-with-deduplication
Pattern for creating hierarchical GitHub issue trees from phased project plans while checking for duplicate/overlapping issues
plan-gated-issue-validation-workflow
Systematic validation pattern for plan-approved GitHub issues with pre-existing deliverables
plan-gated-issue-implementation
Workflow for executing pre-approved GitHub issues with mandatory validation checkpoints
nested-git-repo-stash-safety
How to safely stash changes in a parent repo containing dirty nested git repositories
github-issue-structure-for-personal-finance-tracking
Pattern for organizing financial analysis work across multiple repos (data/config vs. logic separation)
plan-draft-review-artifact-truthfulness-and-issue-body-alignment
Keep plan drafts truthful during adversarial review loops by verifying real provider artifact state on disk and aligning the GitHub issue body to the bounded plan tranche before claiming approval-readiness.
parallel-llm-wiki-gap-to-issues
Use parallel subagents to mine remaining LLM-wiki/document-intelligence gaps, de-duplicate against existing GitHub issues, then create only the strongest bounded follow-on issues.