CLAUDE.md · git:20260215.1f52058 · 2026-02-15 · sha256 4a04ff0d01dc60aa
CLAUDE.md git:20260215.1f52058A
Immutable. This exact content is served forever at /api/v1/blob/4a04ff0d01dc60aa.
# Agents Reflection Skills - Development Guide ## When to Create Tags and Releases **Only create git tags and GitHub releases when skill or plugin files change.** ### Requires New Tag/Release Changes to these files/directories require a new version tag and release: - `skills/*/` - Any skill file changes (SKILL.md, scripts, references, assets) - `.claude-plugin/plugin.json` - Plugin manifest changes - `.claude-plugin/marketplace.json` - Marketplace catalog changes - `LICENSE` - License changes Examples: - Adding a new skill - Updating skill instructions in SKILL.md - Modifying skill scripts - Changing plugin metadata or version ### Does NOT Require New Tag/Release Documentation-only changes do not require tagging: - `README.md` - Documentation and use case updates - `CLAUDE.md` - This file - Commit messages - GitHub-specific files (.github/*) **Rationale:** Users install specific commits via SHA. Documentation updates don't affect functionality, so they don't need version bumps. This keeps the release history clean and meaningful. ## README Maintenance Keep all README files in sync when updating documentation: - `README.md` - Main English documentation - `README.ru.md` - Russian translation - `README.zh.md` - Chinese translation - `README.pt-BR.md` - Brazilian Portuguese translation - `plugins/claude-code-reflection-skills/README.md` - Plugin README (required by plugin spec) When adding/removing skills or changing descriptions, update all five files. ## Versioning Follow semantic versioning (semver): - **MAJOR** (x.0.0) - Breaking changes to skill interfaces - **MINOR** (1.x.0) - New skills or backward-compatible features - **PATCH** (1.0.x) - Bug fixes and minor improvements ## Release Process When skill/plugin files change: 1. Update version in `.claude-plugin/plugin.json` 2. Commit changes 3. Create and push tag: `git tag -a vX.Y.Z -m "Version X.Y.Z" && git push origin vX.Y.Z` 4. Create GitHub release: `gh release create vX.Y.Z --title "vX.Y.Z - Title" --notes "Release notes"` ## Current Structure ``` agents-reflection-skills/ ├── .claude-plugin/ │ └── plugin.json # Version metadata - changes require release ├── skills/ # All changes require release │ ├── mcp-management/ │ ├── hooks-management/ │ ├── settings-management/ │ ├── subagents-management/ │ ├── skills-management/ │ └── plugins-management/ ├── README.md # Documentation - no release needed ├── CLAUDE.md # This file - no release needed └── LICENSE # Changes require release ```