michtio/craftcms-claude-skills / skills/craft-plugin-release
craft-plugin-release
VerifiedReleasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist serves.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.3 KB |
| references/history-rewrites.md | markdown | 3.7 KB |
| references/path-repositories.md | markdown | 3.3 KB |
references/path-repositories.md
View on GitHub# Composer Path Repositories for Multi-Plugin Development
Local development across several plugins usually means a host project whose `composer.json` points `path` repositories at plugin checkouts. The semantics below are the ones that produce silent, expensive surprises. (For what belongs in the *plugin's own* committed manifest — never `../*` path repos — see the `craft-php-guidelines` skill's `references/tooling.md`, Composer Hygiene.)
## A path repository is canonical
If a `path` repository supplies a package name, that package's Packagist versions are **dropped from the resolution pool entirely**. Composer's own documentation states it verbatim: *"That repository is canonical so the lower priority repo's packages are not installable."*
Consequences:
- A constraint the local checkout can't satisfy is a **hard resolution failure** — never a quiet fallback to the published version. If the host requires `^1.8` and the checkout says `1.7.x`, the resolve fails even though Packagist has `1.8.0`.
- "It resolved fine" therefore means the *local* copy satisfied everything, which is a different claim from "the published package satisfies everything."
## No `exclude` option
A wildcard entry supplies **every** directory under it:
```json
{ "type": "path", "url": "/path/to/plugins/*" }
```
There is no way to carve one directory out — `path` repositories have no `exclude` option. The only escapes are enumerating entries individually or moving the directory out of the wildcard's reach. Plan for this before adopting a wildcard: the first time one checkout needs to be excluded (an experiment, a fork, a broken clone), the wildcard has to be unwound.
## `extra.branch-alias` makes a version-less checkout usable
A checkout whose `composer.json` omits `version` publishes as `dev-<branch>`, which satisfies no numeric constraint (`version_compare("dev-develop", "1.8.0", ">=")` is false, and `^1.0` doesn't match `dev-develop`). A branch alias in the *plugin's* manifest fixes that:
```json
{
"extra": {
"branch-alias": {
"dev-develop": "1.x-dev"
}
}
}
```
Two rules that matter in practice:
- **Alias the major line (`1.x-dev`), not the minor (`1.7.x-dev`).** A minor-pinned alias recreates the lockstep-bump treadmill the alias exists to avoid — every minor release means editing the alias in every consumer's resolution path.
- **Alias every branch that gets checked out locally.** An uncovered branch fails resolution hard, and release work *does* check out the release branch. If `develop` and `main` (or `master`, or `develop-v5`) can each be the working checkout, each needs an alias entry.
## Two directories can publish the same package name
Composer does not error when two path-repository directories declare the same `name` — it silently picks whichever satisfies the constraints. Observed failure: a `craft-thing/` and a `craft-thing-584/` (a scratch clone) both declaring `acme/craft-thing`; `composer update --dry-run` was green **because** the scratch clone quietly won, masking a genuinely unsatisfiable constraint in the real checkout.
**A clean resolve is not proof of coverage.** When a wildcard path repo is in play, verify *which* directory won:
```bash
composer show acme/craft-thing | grep -E 'source|path'
```
and keep scratch clones outside the wildcard's directory.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |