release-engineer
Skill1 starsChanged 3 months agoMITView on GitHub
Prepare and validate a release: check changelog completeness, version bump consistency, build artifacts, license compliance, and release checklist items, producing a validated release manifest. Use when cutting a new version, preparing packages for distribution, or auditing release readiness.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- soumyaRauth/skills-hubtheir own version, first seen Aug 25, 2026
- 3loveljw2/agent-identity-kittheir own version, first seen Aug 14, 2026
- CODE-SAURABH/OpenSkillstheir own version, first seen Jul 25, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- soumyaRauth/skills-hub★ 10same name
- CODE-SAURABH/OpenSkills★ 2same name
- 3loveljw2/agent-identity-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- codebase-architectSkill
- deep-debuggerSkill
- dependency-doctorSkill
- documentation-engineerSkill
- performance-engineerSkill
- refactor-engineerSkill
- repo-resurrectionSkill
- security-auditorSkill
- test-engineerSkill
The file
Files
Release Engineer
Release readiness được CHỨNG MINH bằng checklist chạy thật, không khai báo. Pipeline: read state → check items thật → build artifact → verify artifact → manifest.
Quy trình (5 bước)
- Đọc trạng thái: current version (từ package metadata), git tag gần nhất, CHANGELOG entries chưa release.
- Check items thật (script): CHANGELOG entry tồn tại cho version mới? version bump nhất quán (metadata == tag == changelog)? tests pass? build artifact tạo được? license file tồn tại? binary không lọt vào artifact source dist?
- Build artifact: chạy build command thật của repo (python build, npm pack, cargo build).
- Verify artifact: artifact tồn tại, size hợp lý, chứa đủ file cần (entry point, LICENSE), không chứa file nhạy cảm (secret scan nhanh).
- Manifest: output JSON release manifest — mọi item pass/fail với evidence.
Nguyên tắc
- Không tag/publish tự động — skill chỉ chuẩn bị + verify, publish là decision của người.
- Mọi check có evidence (file path, hash, command output).
- Version scheme tuân thủ semver; giải thích major/minor/patch choice.
Scripts
scripts/release_check.py <repo> [--version NEXT]— chạy mọi check, output manifest JSON.
References
- CHECKLIST-REFERENCE.md
- SEMVER-GUIDE.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.