release-closeout-engineer
Finalizes workstreams by generating commit messages, changelogs, and documentation updates.
Install
mkdir -p .claude/skills/release-closeout-engineer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12579" && unzip -o skill.zip -d .claude/skills/release-closeout-engineer && rm skill.zipInstalls to .claude/skills/release-closeout-engineer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Close out a completed workstream by updating README artifacts when needed, producing a commit message, and applying changelog-ready content when the work is ready for commit. Use after review when a stable checkpoint is ready.Key capabilities
- →Determine if README updates are required
- →Produce final README file content
- →Prepare a commit message suggestion in English
- →Prepare and apply changelog-ready content
- →Keep closeout artifacts concise, accurate, and aligned with scope
How it works
The skill closes out a completed workstream by assessing README update needs, generating a commit message, and preparing changelog content.
Inputs & outputs
When to use release-closeout-engineer
- →Finalize project task
- →Update project documentation
- →Generate changelogs
About this skill
Release Closeout Engineer
Load minimal context first
- Load
.github/AGENTS.md. - Load
.github/copilot-instructions.md. - Load
.github/instruction-routing.catalog.yml. - Load
.github/instructions/repository-operating-model.instructions.md. - Load
.github/instructions/super-agent.instructions.md. - Load
.github/instructions/feedback-changelog.instructions.md. - Load
.github/instructions/readme.instructions.mdwhen README files are in scope. - Reuse the shared
$docs-release-engineerskill for documentation and changelog behavior.
Responsibilities
- determine whether README updates are required for the completed workstream and produce the final file content when they are
- prepare a commit message suggestion in English using repository commit conventions
- prepare and apply changelog-ready content when the change belongs in version history
- keep closeout artifacts concise, accurate, and aligned with the implemented scope
Output contract
- closeout summary
- README actions or confirmation that no README update is needed
- structured README updates when files must be rewritten
- suggested commit message
- changelog summary plus structured changelog update payload
- ready-to-commit flag
When not to use it
- →When the workstream is not completed or reviewed
- →When a stable checkpoint is not ready for commit
Limitations
- →Requires loading specific context files like .github/AGENTS.md
- →Requires using repository commit conventions for commit messages
- →Requires the change to belong in version history for changelog content
How it compares
This skill standardizes the closeout process for workstreams by generating required documentation and commit artifacts, unlike manual, unstructured completion steps.
Compared to similar skills
release-closeout-engineer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release-closeout-engineer (this skill) | 0 | 4mo | No flags | Intermediate |
| openspec-archive-change | 4 | 6mo | Review | Intermediate |
| session-wrap | 1 | 7mo | Review | Intermediate |
| semantic-commits | 0 | 4mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by ThiagoGuislotti
View all by ThiagoGuislotti →You might also like
openspec-archive-change
studyzy
归档实验性工作流中已完成的变更。当用户想要在实现完成后最终确定并归档变更时使用。
session-wrap
team-attention
This skill should be used when the user asks to "wrap up session", "end session", "session wrap", "/wrap", "document learnings", "what should I commit", or wants to analyze completed work before ending a coding session.
semantic-commits
lipkau
>-
tbd
jlevy
|-
preserve
markwharton
Preserve the most recently approved plan to docs/plans/
session-handoff
Maximumsoft-Co-LTD
Serialize mid-session context into a handoff doc so the next session (or engineer) can resume without cold-start