Menu
Commit conventions, branching, anchors in messages, and the git safety rules. Load for any git operation beyond status/diff.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Context engineering — memory navigation, textual graph traversal, progressive disclosure, recovery. Load when assembling context for a task or when lost.
Implementation-side security discipline — headers, dependencies, secrets, authz. Load for hardening work (sec-ops domain).
Anti-generic-AI design discipline — bans, tells, and the slop test. Load for ANY new UI surface or visual redesign. Inspired by Impeccable (Apache 2.0).
Motion & animation discipline — purpose, performance, reduced-motion. Load when work involves animation, transitions or scroll effects.
Microcopy discipline — buttons, errors, empty/loading/success states, alt text. Voice and tone come from the project's memory, not from this skill.
Infrastructure composition patterns — immutable infra, GitOps, golden images, cattle-not-pets, day-2 thinking. Tool-agnostic.
| name | git-workflow |
| description | Commit conventions, branching, anchors in messages, and the git safety rules. Load for any git operation beyond status/diff. |
The git-safety hook blocks: push (any) · --force/--force-with-lease · --no-verify · reset --hard · clean -f · branch -D · deleting remote refs.
Why: repos may auto-deploy on push (Vercel/Actions) — push = production. "Work is done" is NOT authorization to publish. The human says push, or nothing is pushed. Authorized by the human? They set BERSERQIR_GIT_ALLOW=1 for that command.
Local commits are safe and encouraged (reversible). Stop at commit; list what's ready to push in your report.
type(scope): subject — types: feat fix refactor test docs chore perf ci.
FEAT-…/ADR-NNN/DEBT-NNN in the body — commit messages are graph edges (core/skills/context-eng)feat(contact): add rate limiting to contact endpoint
Implements FEAT-2026-07-08-contact-rate-limit per ADR-014.
<type>/<anchor-or-slug> — e.g. feat/contact-rate-limit, fix/DEBT-003. Branch from main, short-lived, delete after merge (via PR, not -D).
Running more than one harness session on the same repo? Give each its own worktree instead of stash-dancing on one checkout:
git worktree add ../repo-feat-x feat/x # session 2 works here
git worktree remove ../repo-feat-x # after merge
One session per worktree, one branch per worktree — sessions never trample each other's files, each /sprint commits in isolation, and memory conflicts surface at merge (a worktree shares .git but not the working files). In-session subagents don't need this: they share one checkout by harness design — that's what the parallelism protocol's disjoint file scopes are for (core/protocols/parallelism.md).
Working tree reviewed (git status + git diff --staged) · no unrelated files staged · secrets scan clean (hook enforces) · tests relevant to the diff pass.