Skip to content
Agentmart
Submit a tool

release-readiness

Prepare work for merge request and release with a checklist covering evidence, tests, review, security, and rollback considerations.

Skill by hoskengadu

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/hoskengadu-release-readiness

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Prepare work for merge request and release with a checklist covering evidence, tests, review, security, and rollback considerations.

Use cases: security

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/release-readiness

What's inside

Skill name
release-readiness
Description
Prepare work for merge request and release with a checklist covering evidence, tests, review, security, and rollback considerations.
License
MIT
Metadata
short-description: Merge request and release readiness
Instructions
21 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Release Readiness

Use this skill when the work is close to merge, needs a final quality pass, or must be summarized for review.

## Readiness Checklist

- The request is implemented and aligned with the stated scope.
- The change was validated with meaningful tests or checks.
- Known risks and tradeoffs are documented.
- Security-sensitive paths were reviewed.
- The final summary separates facts from assumptions.
- The reviewer has enough context to approve or request changes.

## Merge Request Guidance

- Keep the description factual and structured.
- Include what changed, why it changed, how it was validated, and any remaining risk.
- Avoid claiming zero risk unless the evidence truly supports it.
- If the branch is not ready, say what is still missing.

From hoskengadu/software-engineering-skills, MIT.

More from hoskengadu/software-engineering-skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 20, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from hoskengadu

Cite this page

release-readiness skill. Agent Mart. https://agentmart.dev/skills/hoskengadu-release-readiness (last updated 2026-10-24)