git-workflow
Defines branch naming conventions, PR template requirements, commit message format, discovered-issues escalation policy, and task tracking conventions. Load when committing, pushing, or opening PRs.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Git Workflow & Delivery
NEVER push directly to main. All changes go through a feature/fix branch → PR.
Branch & Commit Rules
| Rule | Detail |
|---|---|
Branch from main | git checkout -b <type>/<ticket-id>-<slug> |
| Types | fix, feat, chore, refactor, perf, docs |
| Commit messages | Must reference issue ID — TAS-42: Fix token refresh |
| No force-push | Never --force or --amend on shared branches; --force-with-lease on personal only |
| No secrets | No tokens/keys in commits, PR descriptions, or output (rotate immediately if leaked) |
Delivery Checklist (Every Task)
- Branch
<type>/<ticket-id>-<slug>frommain - Atomic commits referencing issue ID
- Push branch to origin
- Open PR (do NOT merge):
GH_PAGER=cat gh pr create --base main --title "TAS-XX: …" --body "Resolves TAS-XX" - Update issue with PR URL
Discovered Issues Policy
Inherits: discovered-issues-policy
Task Tracking
Tracked in the task tracker (tracker-config.md). Team Lead creates/updates issues via MCP. Load task-management skill for conventions.
If MCP tools unavailable: Document planned issues (title + AC) in output, use "N/A" (no tracker) or "TAS-PENDING" (tracker configured), proceed with work, update IDs when available.
- Repository
- monkilabs/opencastle
- Commit
f5c8508
- Last updated
- Created
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.