Deploy to a target environment after running pre-flight checks. Only invoke manually.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
!git status --short
!git log --oneline -5
Deploy to: $ARGUMENTS
If $ARGUMENTS is empty, stop immediately. Report: "No environment specified. Invoke as: /safe-deploy <environment> (e.g., /safe-deploy staging or /safe-deploy production)."
Check the git status output above. If it shows any modified, untracked, or staged files, stop here.
Report: "Deploy aborted: the working tree has uncommitted changes. Commit or stash them before deploying to $ARGUMENTS."
Do not proceed past this step if there are uncommitted changes.
Run:
npm test
If any test fails, stop here. Report the failing test names and do not proceed.
Run:
npm run build
If the build fails, report the full error output and stop. Do not proceed.
Construct a tag name:
deploy-$ARGUMENTS-<YYYYMMDD>-<HHMMSS>
Use the current UTC date and time. For example, a production deploy on 2026-05-13 at 14:32:07 UTC produces: deploy-production-20260513-143207.
Run:
git tag deploy-$ARGUMENTS-<YYYYMMDD>-<HHMMSS>
Run:
git push origin deploy-$ARGUMENTS-<YYYYMMDD>-<HHMMSS>
If the push fails, report the error. Do not retry automatically.
Print a final summary:
Deploy initiated.
Environment: $ARGUMENTS
Tag: deploy-$ARGUMENTS-<YYYYMMDD>-<HHMMSS>
Commit: <git rev-parse HEAD output>
Time: <YYYY-MM-DD HH:MM:SS UTC>
If any step failed, do not print this summary. The failure report for the failing step is the final output.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
The English summary is being prepared. Showing the original description.
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
The English summary is being prepared. Showing the original description.
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
The English summary is being prepared. Showing the original description.
Create a git branch named after a GitHub issue.
The English summary is being prepared. Showing the original description.
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.