safe-workflow

SAFe workflow discipline enforces standardized practices for branch naming, commit messages, and rebase-first history across teams. This Skill applies SAFe guidelines to Linear tickets, ensuring consistent branch conventions, required commit formats, and PR validation to reduce errors and improve traceability.

Branch naming convention in SAFe ties directly to ticket identifiers. This Skill enforces a naming pattern derived from your Linear ticket prefix—for example, TICKET-123—ensuring branches are traceable to work items and searchable across your repository.

Rebase-first workflow prevents merge commits and keeps history linear for easier debugging. This Skill guides you through rebasing commits onto the latest main before opening a PR, maintaining clean history and reducing integration conflicts.

SAFe PR descriptions link changes back to tickets and cross-team coordination processes. This Skill provides PR templates and pre-PR validation checklists to ensure quality gates are met and all required fields—ticket reference, change summary, testing notes—are documented.

Start work using the /start-work command with your ticket prefix (for example, /start-work TICKET-XXX). This Skill generates the enforced branch name, guides commit message formatting, and sets up your rebase-first workflow from ticket to PR submission.

Yes. This Skill includes CI validation as part of SAFe development workflow, ensuring commits and branches pass automated checks before PR submission. It integrates with your CI pipeline to enforce quality gates and cross-team coordination requirements.