release-patterns
>
pinned to #a10f722updated 2 weeks ago
Ask your AI client: “install skills/release-patterns”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/release-patternsmetahub onboarded this repo on the author's behalf.
If you own github.com/bybren-llc/safe-agentic-workflow on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
363
Last commit
2 weeks ago
Latest release
published
- #agile-methodology
- #ai-agents
- #ai-assisted-development
- #claude-code
- #commands
- #dark-factory
- #developer-tools
- #evidence-based-development
- #harness
- #hooks
- #methodology
- #multi-agent
- #safe-framework
- #scaled-agile-framework
- #skills
- #software-development
- #software-engineering
- #task-orchestration
- #whitepaper
About this skill
Pulled from SKILL.md at publish time.
> **TEMPLATE**: This skill uses `{{PLACEHOLDER}}` tokens. Replace with your project values before use.
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.a10f722· 2 weeks ago
Documentation
121Description qualityfail
Only 1 words · 1 chars — minimum 15 words
A skill's description doubles as its trigger. Describe what it does, when to use it, what file types it handles.
README is present and substantialwarn
README present but its contents couldn't be read this scan
Transient fetch issue — re-run the eval to grade the README's substance.
Tags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Release history
1- releasecurrenta10f722warn2 weeks ago
Contents
TEMPLATE: This skill uses
{{PLACEHOLDER}}tokens. Replace with your project values before use.
Purpose
Ensure consistent PR creation, CI/CD validation, and release coordination following rebase-first workflow.
When This Skill Applies
- Creating pull requests
- Running pre-PR validation
- Checking CI/CD status
- Coordinating merge timing
- Verifying rebase status
Stop-the-Line Conditions
FORBIDDEN Patterns
# FORBIDDEN: Missing ticket reference
gh pr create --title "feat: add feature" # Missing [{{TICKET_PREFIX}}-XXX]
# FORBIDDEN: Using squash/merge commits (breaks linear history)
gh pr merge --squash
gh pr merge --merge
# FORBIDDEN: Skipping CI validation
git push origin feature # Without {{CI_VALIDATE_COMMAND}} first
# FORBIDDEN: Pushing without rebase
git push origin feature # When branch is behind {{MAIN_BRANCH}}
CORRECT Patterns
# CORRECT: Ticket reference in title
gh pr create --title "feat(scope): description [{{TICKET_PREFIX}}-XXX]"
# CORRECT: Rebase merge only
gh pr merge --rebase --delete-branch
# CORRECT: CI validation before push
{{CI_VALIDATE_COMMAND}} && git push --force-with-lease
# CORRECT: Always rebase first
git fetch origin && git rebase origin/{{MAIN_BRANCH}}
git push --force-with-lease origin {{TICKET_PREFIX}}-XXX-description
Pre-PR Checklist (MANDATORY)
Before creating any PR:
- Branch name:
{{TICKET_PREFIX}}-{number}-{description} - Commits follow:
type(scope): description [{{TICKET_PREFIX}}-XXX] - Rebased on latest {{MAIN_BRANCH}}:
git fetch origin && git rebase origin/{{MAIN_BRANCH}} - CI passes locally:
{{CI_VALIDATE_COMMAND}} - Linear history: No merge commits (
git log --oneline --graph -10)
CI/CD Validation Command
# MANDATORY before any PR
{{CI_VALIDATE_COMMAND}} && echo "READY FOR PR" || echo "FIX ISSUES FIRST"
PR Creation Template
gh pr create --title "feat(scope): description [{{TICKET_PREFIX}}-XXX]" --body "$(cat <<'EOF'
## Summary
Implements [feature/fix] as specified in ticket {{TICKET_PREFIX}}-XXX.
**Ticket**: https://linear.app/{{LINEAR_WORKSPACE}}/issue/{{TICKET_PREFIX}}-XXX
## Changes Made
- Change 1
- Change 2
## Testing
{{CI_VALIDATE_COMMAND}}
# All checks passed
## Pre-merge Checklist
- [x] Rebased on latest {{MAIN_BRANCH}}
- [x] CI passes
- [x] Ticket referenced
EOF
)"
Merge Strategy
ONLY use rebase merge:
# CORRECT
gh pr merge --rebase --delete-branch
# NEVER
gh pr merge --squash # Loses commit history
gh pr merge --merge # Creates merge commits
QAS Gate (MANDATORY)
Before merging any PR, invoke QAS for independent review:
Prompt: "Review PR #XXX for {{TICKET_PREFIX}}-YYY. Validate commit format,
CI status, patterns."
Release Workflow
Version Bump
# Determine version bump based on commits
# feat: -> minor bump
# fix: -> patch bump
# feat!: or BREAKING CHANGE -> major bump
# Tag the release
git tag -a v{{VERSION}} -m "Release v{{VERSION}}"
git push origin v{{VERSION}}
GitHub Release
gh release create v{{VERSION}} --title "v{{VERSION}}" --notes "$(cat <<'EOF'
## Changes
- feat(scope): description [{{TICKET_PREFIX}}-XXX]
- fix(scope): description [{{TICKET_PREFIX}}-YYY]
## Breaking Changes
None
## Migration Steps
None required
EOF
)"
Branch Sync (Post-Release)
# After release merge, sync branches
git checkout {{MAIN_BRANCH}} && git pull origin {{MAIN_BRANCH}}
git checkout dev && git pull origin dev
git merge {{MAIN_BRANCH}} # Only case where merge commits are allowed
git push origin dev
Authoritative References
- PR Template:
.github/pull_request_template.md - Workflow Guide:
CONTRIBUTING.md(Pull Request Process section) - CI/CD Pipeline:
docs/ci-cd/CI-CD-Pipeline-Guide.md - Agent Workflow SOP:
docs/sop/AGENT_WORKFLOW_SOP.md
Reviews
No reviews yet. Be the first.
Related
orchestration-patterns
>
migration-patterns
>
deployment-sop
>
mh install skills/release-patterns