Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →bybren-llc/safe-workflow
SAFe development workflow guidance including branch naming conventions, commit message format, rebase-first workflow, and CI validation.
Passed 20 of 22 test cases with the skill, and 12 of 22 without it.
and 9 more in the full report
9 fixed11 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am opening a branch to fix a login timeout bug tracked under ticket FEAT-99. How should the branch be named?
| Checked | Without skill | With skill |
|---|---|---|
| Formats branch name as FEAT-99-fix-login-timeout without type prefix. | Missed | Passed |
The instructions your model reads when the skill loads.
TEMPLATE: This skill uses
{{TICKET_PREFIX}}as a placeholder. Replace with your project's ticket prefix (e.g.,WOR,PROJ,FEAT).
Enforce SAFe-compliant git workflow with standardized branch naming, commit message format, and rebase-first merge strategy.
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)
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 |
test cases passed, vs 12 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.