safe-workflow
>
pinned to #a10f722updated last week
Ask your AI client: “install skills/safe-workflow”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/safe-workflowmetahub 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
last week
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 `{{TICKET_PREFIX}}` as a placeholder. Replace with your project's ticket prefix (e.g., `WOR`, `PROJ`, `FEAT`).
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.a10f722· last week
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- releasecurrenta10f722warnlast week
Contents
TEMPLATE: This skill uses
{{TICKET_PREFIX}}as a placeholder. Replace with your project's ticket prefix (e.g.,WOR,PROJ,FEAT).
Purpose
Enforce SAFe-compliant git workflow with standardized branch naming, commit message format, and rebase-first merge strategy.
When This Skill Applies
- Starting work on a ticket
- Creating commits or branches
- Asking about PR workflow or contribution guidelines
- Asking "how should I commit this?"
Branch Naming Convention
Format: {{TICKET_PREFIX}}-{number}-{short-description}
# Good
{{TICKET_PREFIX}}-447-create-safe-workflow-skill
{{TICKET_PREFIX}}-123-fix-login-redirect
# Bad
feature/add-dark-mode (missing ticket number)
john-new-feature (personal naming)
Commit Message Format
Format: type(scope): description [{{TICKET_PREFIX}}-XXX]
| Type | When to Use |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation only |
refactor | Code restructuring |
test | Adding or updating tests |
chore | Maintenance, dependencies |
feat(harness): create safe-workflow skill [{{TICKET_PREFIX}}-447]
fix(auth): resolve login redirect [{{TICKET_PREFIX}}-57]
Rebase-First Workflow
# 1. Start from latest main
git checkout {{MAIN_BRANCH}} && git pull origin {{MAIN_BRANCH}}
# 2. Create feature branch
git checkout -b {{TICKET_PREFIX}}-{number}-{description}
# 3. Make commits
git commit -m "type(scope): description [{{TICKET_PREFIX}}-XXX]"
# 4. Before pushing - rebase
git fetch origin && git rebase origin/{{MAIN_BRANCH}}
# 5. Push with force-with-lease
git push --force-with-lease
Pre-PR Checklist
- Branch name follows convention
- All commits have ticket reference
- Rebased on latest main
- CI passes:
{{CI_VALIDATE_COMMAND}}
Evidence Template
When closing a ticket, attach evidence:
**Work Evidence**
**Ticket**: {{TICKET_PREFIX}}-XXX
**Branch**: {{TICKET_PREFIX}}-XXX-description
**PR**: #NNN
**Commits:**
- type(scope): description
**Validation:**
- CI: PASS
- Tests: X/X passing
- Lint: Clean
Reference
- CONTRIBUTING.md - Full contributor guide
- AGENTS.md - Development context and agent roles
Reviews
No reviews yet. Be the first.
Related
orchestration-patterns
>
migration-patterns
>
deployment-sop
>
mh install skills/safe-workflow