Release Process Skill
Earned knowledge from the v0.9.0→v0.9.1 incident. Every agent involved in releases MUST read this before starting release work. Published by microsoft in frontier-agentic-devops-rvas.
What is Release Process Skill?
Earned knowledge from the v0.9.0→v0.9.1 incident. Every agent involved in releases MUST read this before starting release work. Published by microsoft in frontier-agentic-devops-rvas. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Documentation
- Testing use cases
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use Release Process Skill
- Use it for testing.
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/frontier-agentic-devops-rvas
- Skill file: .squad/templates/skills/release-process/SKILL.md
What it does
Earned knowledge from the v0.9.0→v0.9.1 incident. Every agent involved in releases MUST read this before starting release work.
Skill instructions
Release Process Earned knowledge from the v0.9.0→v0.9.1 incident. Every agent involved in releases MUST read this before starting release work. SCOPE ✅ THIS SKILL PRODUCES: - Pre-release validation checks that prevent broken publishes - Correct npm publish commands (never workspace-scoped) - Fallback procedures when CI workflows fail - Post-publish verification steps ❌ THIS SKILL DOES NOT PRODUCE: - Feature implementation or test code - Architecture decisions - Documentation content Confidence: high Established through the v0.9.1 incident (8-hour recovery). Every rule below is battle-tested. Context Squad publishes two npm packages: @bradygaster/squad-sdk and @bradygaster/squad-cli. The release pipeline flows: dev → preview → main → GitHub Release → npm publish. Brady (project owner) triggers releases — the coordinator does NOT. Rules (Non-Negotiable) 1. Coordinator Does NOT Publish The coordinator routes work and manages agents. It does NOT run npm publish, trigger release workflows,
Explore related resources
Frequently asked questions
What is Release Process?
Release Process is a open-source AI agent skill with Copy skill directory. Earned knowledge from the v0.9.0→v0.9.1 incident. Every agent involved in releases MUST read this before starting release work.
Who is Release Process best for?
Release Process is best for reusing agent instructions, scripts, and references, testing workflows, documentation workflows.
How do I install Release Process?
Install or run Release Process using Copy skill directory. Check Release Process for the latest setup command.
Is Release Process actively maintained?
Release Process may need a closer maintenance check before production use.
Auto-fetched from GitHub.
