kaiord: Skill for Claude Code

.claude/skills/guidelines/git-strategy/SKILL.md

git-strategy is a skill for Claude Code from pablo-albaladejo/kaiord. It costs 32 tokens per session (853 once invoked), scanned A, original, MIT.

A Git workflow guide covering commits, branches, pull requests, and checks. Git is the version-control system used to track code changes.

In plain words
What is it for?
Use it when creating commits, opening pull requests, writing change descriptions, branching, or running commands that modify Git history.
Why use it?
It keeps changes reviewable and prevents history changes that bypass required checks. It also standardizes commit messages so automated tools can validate them.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is pablo-albaladejo/kaiord's own configuration. It tells Claude Code how to work on kaiord itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kaiord configures →

Reuse

Borrowing it

Nothing to install: this file belongs to pablo-albaladejo/kaiord. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/pablo-albaladejo/kaiord/main/.claude/skills/guidelines/git-strategy/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/pablo-albaladejo/kaiord

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for git-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/pablo-albaladejo/kaiord/git-strategy.svg)](https://agentmods.dev/skills/pablo-albaladejo/kaiord/git-strategy)
Your own site
<a href="https://agentmods.dev/skills/pablo-albaladejo/kaiord/git-strategy"><img src="https://agentmods.dev/badge/skills/pablo-albaladejo/kaiord/git-strategy.svg" alt="Measured on agentmods" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 853 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00853
Opus 5 $0.00016 $0.00426
Sonnet 5 $0.00006 $0.00171
Haiku 4.5 $0.00003 $0.00085

Measured 8d ago against content hash 80a50ae370d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

git-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/guidelines/git-strategy/SKILL.md · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Strategy — Kaiord

PRs are mandatory

All changes go through a PR — even one-line fixes. NEVER push directly to main.

Hooks must never be bypassed

NEVER use HUSKY=0, --no-verify, or any mechanism that skips pre-commit hooks. If a hook fails, fix the underlying issue.

Conventional commits

Format: type(scope): description

Single-scope subjects are normative — multi-scope (refactor(core,fit,tcx): ...) is rejected by commitlint.config.mjs.

Source of truth: commitlint.vocab.mjs + the block below. Drift between the two (insertion, deletion, OR reorder) fails CI via scripts/check-commitlint-config.test.mjs. Enforcement: commitlint.config.mjs

  • .husky/commit-msg + scripts/check-commitlint-config.test.mjs.
# types
feat
fix
chore
test
docs
refactor
perf

# scopes
core
fit
tcx
zwo
tanita
garmin
garmin-connect
ai
cli
mcp
i18n
spa-editor
garmin-bridge
train2go-bridge
tanita-bridge
whoop
trainingpeaks
whoop-bridge
trainingpeaks-bridge
bridge-core
analytics
landing
docs-site
openspec
ci
docs
scripts
deploy
release
deps
deps-dev
e2e

Enforcement: commitlint.config.mjs + .husky/commit-msg + scripts/check-commitlint-config.test.mjs.

Changesets

  • One changeset per change (not per package) — packages in the linked array bump together
  • The changeset is the last commit on the feature branch before requesting review
  • Run pnpm exec changeset and follow the interactive prompt
  • garmin-bridge and train2go-bridge are in the linked array — they need changesets when changed
  • workout-spa-editor is not in linked or ignore — needs a changeset if changed
  • The private: true flag prevents publishing but does not exempt a package from changesets

Changeset exceptions

A changeset is NOT required when:

  1. The change touches only repo-root tooling (scripts/, .husky/, root package.json devDeps).
  2. The change is internal to a published package and exported symbol names are unchanged (e.g., file renames preserving the public API).
  3. The change is test-only or docs-only.

Read the full file on GitHub · 119 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 119 lines · 32 tokens per session scan A 80a50ae370d3

Subscribe to this mod's changes

git-strategy is a skill published in the GitHub repository pablo-albaladejo/kaiord (9 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 853 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

update-skills

Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says "learn!", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.

microsoft/vscode · 51 tokens

github-copilot-upgrader

Use this to update the Github Copilot CLI/SDK.

microsoft/vscode · 18 tokens

sync

Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.

microsoft/vscode · 52 tokens

merge

Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.

microsoft/vscode · 31 tokens

triage-contributor-pr

Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…

prisma/orm · 131 tokens

contrib-pr

Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.

prisma/orm · 65 tokens