AGENTS.md · git:20261108.c2f94bf · 2026-11-08 · sha256 d81cedd40dbeddc5
AGENTS.md git:20261108.c2f94bfA
Immutable. This exact content never changes and is served at /api/v1/blob/d81cedd40dbeddc5.
# skills — working in this repo
This repo is a Claude Code **plugin marketplace** of agent skills. Each skill is a plugin under `plugins/`.
## Branching & releases — follow GitFlow
This repo **ships** the GitFlow skill at [`plugins/gitflow/SKILL.md`](plugins/gitflow/SKILL.md) — and it follows it. That file is the **source of truth**; use it for any branch/release work here. The essentials:
- New skill or edit → `feature/<name>-<ts>` from `develop` → finish `--no-ff` into `develop`.
- New version → `release/<version>` from `develop` → **bump the `version` in EVERY `plugins/*/.claude-plugin/plugin.json` to the release version** on the branch → Release Finish (merge into `develop` then `main`, annotated tag `v<version>`, atomic push).
## Versioning — lockstep
All plugins version **as a single block** (the same model as the libraries' central `VersionPrefix`): there is ONE version — the release's — and every `plugins/*/.claude-plugin/plugin.json` carries it. A release bumps **all** of them, changed or not, so plugin versions == git tag == GitHub Release, and any installed skill traces back to the exact tag. Never bump a single plugin on its own.
Bump one-liner (run on the `release/<version>` branch):
```bash
find plugins -name plugin.json -path "*/.claude-plugin/*" \
-exec sed -i 's/"version": "[^"]*"/"version": "<version>"/' {} +
```
- Use git's **default merge message** (`--no-ff --no-edit`, never `-m`).
- Commit with the identity git already has for this repo (its own, set at repo level); **no** `Co-Authored-By` / Claude / Anthropic trailer.
- Branch prefixes only: `feature` / `bugfix` / `release` / `hotfix`.
## Adding a skill
See [CONTRIBUTING.md](CONTRIBUTING.md): create `plugins/<plugin>/SKILL.md` and its `.claude-plugin/plugin.json` (name, description, the lockstep version, author, and — for a stack skill — `dependencies` on the generic skills it realizes), register it in `.claude-plugin/marketplace.json` with the same description, add a row to `README.md`.
Two kinds of skill, kept apart on purpose: the **generic** ones (`solid`, `clean-architecture`, `ddd`, `testing`, `logging`, `messaging`, `gitflow`, `pnpm`) state principles for any stack and never name a `-dotnet` skill or a .NET type; each **`-dotnet`** skill is the .NET realization of one of them and depends on it. Library mechanics (what `JorgeCostaMacia.*` does inside) stay in the libraries' READMEs; a skill says how the code uses them.