opencode-config/.opencode/skills/branch/SKILL.md at a8f9aa0bc6f773d319a2622d7663f283417e157d - slaid098/opencode-config - Forgejo: Beyond coding. We forge.

slaid098/opencode-config

Sergey a8f9aa0bc6

feat: migrate .opencode/ config from opencode (#23 )

* feat: migrate .opencode/ config from opencode

* refactor: rename repo refs and sanitize for public

* docs(handoff): add pr-7 handoff + ADR-002

* docs(handoff): fix PR number

* docs: update project map with .opencode/ structure

---------

Co-authored-by: opencode-agent <agent@slaid098.dev>

2026-07-23 22:57:39 +03:00

674 B

Raw Blame History

name: branch description: Use when creating a new git branch for work. Describes branch naming convention and creation workflow. Format: type/scope/kebab-description.

Branch format

type/scope/kebab-description

Examples

feat/auth/add-refresh-token-rotation
fix/api/handle-null-response
chore/deps/update-pytest
refactor/db/simplify-queries

Rules

Always branch from main
Before creating a branch, discuss with the user:
- Confirm the branch name
- Confirm the scope
- Make sure you understand the task
Push the branch to remote after creation

The type and scope follow the same conventions as commit messages.