Skip to content
Back to skills

Safe Workflow

ASecurity

SAFe development workflow guidance including branch naming conventions, commit message format, rebase-first workflow, and CI validation. Use when starting work on a Linear ticket, preparing commits, creating branches, writing PR descriptions, or asking about contribution guidelines.

  • 404 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 6, 2026
developmentgobashgitdocumentation

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 6, 2026

npx -y skills add bybren-llc/safe-agentic-workflow --skill safe-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Safe Workflow?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Safe Workflow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bybren-llc-safe-workflow-24ff8318/badge)](https://www.skillsdirectory.com/skills/bybren-llc-safe-workflow-24ff8318)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: safe-workflow
description: SAFe development workflow guidance including branch naming conventions, commit message format, rebase-first workflow, and CI validation. Use when starting work on a Linear ticket, preparing commits, creating branches, writing PR descriptions, or asking about contribution guidelines.
---

# SAFe Workflow Skill

> **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}`

```text
# 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     |

```text
feat(harness): create safe-workflow skill [{{TICKET_PREFIX}}-447]
fix(auth): resolve login redirect [{{TICKET_PREFIX}}-57]
```

## Rebase-First Workflow

```bash
# 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

1. Branch name follows convention
2. All commits have ticket reference
3. Rebased on latest main
4. CI passes: `{{CI_VALIDATE_COMMAND}}`

## Reference

- **CONTRIBUTING.md** - Full contributor guide
- **GEMINI.md** - Development commands

Files in this skill

  • README.md1.7 KB
  • SKILL.md2.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.