Skip to content
Agentmart
Submit a tool

release-and-deploy

Versioning (vX.Y.Z), branches, CI/CD, changelog.

Skill by EtienneP-26

IndexedMIT★ 2
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/etiennep-26-release-and-deploy

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Versioning (vX.Y.Z), branches, CI/CD, changelog. Use when setting up or changing releases, deployment or pipelines.

Use cases: devops

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/release-and-deploy

What's inside

Skill name
release-and-deploy
Description
Versioning (vX.Y.Z), branches, CI/CD, changelog. Use when setting up or changing releases, deployment or pipelines.
License
MIT
Instructions
32 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Release and deploy

## Find the project's rules first
1. CONTRIBUTING.md, if present, decides. Follow it.
2. Otherwise infer from the history: `git tag --list`, `git branch -a`, `git log --oneline -30` (delegate to `reader` if large).
3. If neither says, **ask the user** before choosing, and give the trade-off for each option.

## Versioning
- Format `vX.Y.Z` (Semantic Versioning): X for breaking changes, Y for new backward-compatible features, Z for fixes.
- Ask the user whether they want that scheme, and whether pre-releases (`v1.2.0-rc.1`) are needed.
- The version lives in one place (manifest such as package.json or pyproject.toml, or the git tag) and the rest derives from it.

## Branches and environments
Propose, then follow what the user picks. A common simple layout:
- `main`: production, always deployable.
- `dev` (or `develop`): integration, deploys to a dev or staging environment.
- Sub-branches from `dev`: `feat/...`, `fix/...`, `chore/...`, merged by pull request.
Trade-off to state: this is simple and safe for a small team; trunk-based development with short branches and feature flags is faster but needs strong CI and discipline.

## CI/CD pipeline
Minimum stages, in order: install, lint, test, build, then deploy (dev automatically, prod on a version tag or manual approval). Use the platform already in the project (GitHub Actions, GitLab CI...). Secrets go in the platform's secret store, never in the pipeline file.

## Changelog and docs
- Keep a `CHANGELOG.md` in the Keep a Changelog style: Added, Changed, Fixed, Removed, per version, newest first.
- Docs describe the current version; when a release changes behavior, update the docs in the same change and mention the version.

## Cutting a release
1. Tests, lint and `security-check` pass.
2. Bump the version, update CHANGELOG and docs.
3. Commit and tag `vX.Y.Z`. Both are git writes: follow the `git-workflow` skill and ask before pushing the tag.

From EtienneP-26/Noctia, MIT.

Signals

Stars
2
Forks
1
Open issues
0
Last commit (this folder)
Oct 19, 2026 (9 days ago)
Last release
Oct 11, 2026 (17 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from EtienneP-26

Cite this page

release-and-deploy skill. Agent Mart. https://agentmart.dev/skills/etiennep-26-release-and-deploy (last updated 2026-10-24)