dev-release-check
/dev-release-check
Use for pre-release validation, versioning, changelogs, artifacts, smoke tests, rollback notes, and release risk.
- Author
- blueskyxn ↗
- Repository
- codex-is-all-you-need ↗
- Licence
- GPL-3.0
- Last repository change
- 17.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 17.09.2026, without references to retired models or APIs.
GPL-3.0, otwarta.
What it does and when to use it
Use for pre-release validation, versioning, changelogs, artifacts, smoke tests, rollback notes, and release risk.
Original author description
Use for pre-release validation, versioning, changelogs, artifacts, smoke tests, rollback notes, and release risk.
How it works
- Steps
- Output
- Do not
SKILL.md preview
--- name: dev-release-check description: Use for pre-release validation, versioning, changelogs, artifacts, smoke tests, rollback notes, and release risk. metadata: version: "0.3" updated: "2026-06-12" --- # Release check workflow Use this workflow when preparing, reviewing, or validating a software release. ## Steps 1. Identify release target. - Version or tag - Branch or commit - Package or app artifact - Deployment target - Release notes audience 2. Read release sources. - Diff since last release - Changelog - Package metadata - CI status - Build scripts - Docs and migration notes 3. Validate readiness. - Tests - Typecheck/lint/build - Artifact generation - Smoke test - Dependency/security checks if relevant - Backward compatibility and migration notes 4. Prepare release material. - Version bump - Tag plan - Release notes - Known issues - Rollback path - Verification commands 5. Read back final state. - Commit SHA - Tag - Artifact path or URL - CI/check results if remote release is involved ## Output Return: 1. Release target 2. Change summary 3. Validation performed 4. Artifact/tag/state 5. Known risks or rollback notes ## Do not - Do not create tags or publish artifacts unless explicitly asked. - Do not claim CI or release success without reading back the final state. - Do not overstate stability beyond the checks actually run.
Versions
The database has no other skills named dev-release-check.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version fd08eddb32f0 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 2 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100briefbound-release-versioning
Use when the user asks to cut a release, write or update a changelog, decide a semver bump, run pre-release checks, draft release notes, or prepare a rollback plan; do not use for single bug-fix execution, deployment or runtime operations, or contract compatibility analysis itself. - 100release
Automated release workflow and versioning. Use for "release", "version", "publish", and "changelog". - 100release-checklist
Build a release checklist and go/no-go plan covering semantic versioning, changelog, green CI and security gates, signed artifacts, database migrations, feature flags, staged rollout and a tested rollback plan. Use when the user is preparing a release or deploy, cutting a tag,… - 90release-check
Runs a pre-merge or pre-deploy gate with the repo's canonical release script, git state, build and test, migration and env risk, smoke routes, rollback plan, and a go/no-go verdict. Use when asked whether a branch is ready to merge, release, or deploy. - 100release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering… - 90dev-loop-changelog-generator
Use when the user asks about generating changelogs, release notes, conventional commits to changelogs, automated release notes, or CHANGELOG.md management. Do NOT use for: git commit messages (dev-loop-git-workflow), or code review (dev-loop-code-review).