release

Estrelas6

Forks0

Atualizado9 de junho de 2026 às 14:38

Release a new version of adversarial-review (bumps version, tags git, pushes, triggers npm publish)

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

voodootikigod

voodootikigod/adversarial-review

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	release
description	Release a new version of adversarial-review (bumps version, tags git, pushes, triggers npm publish)
license	Apache-2.0
user-invocable	true
metadata	{"version":"1.0.0","internal":true}

Release

Use this command to release a new version of adversarial-review.

Arguments

First positional argument: Version bump type — "patch", "minor", or "major". Defaults to "minor" if not specified.

Steps

Determine the new version. Read the current version from package.json. Apply the requested semver bump (default "minor") to compute the new version number.
Verify preconditions:
- Working tree is clean (git status --porcelain is empty)
- On the main branch
- Up to date with remote (git pull --dry-run shows no changes)
- Tests pass (npm test)
Bump version:
- Update the "version" field in package.json
- Update metadata.version in skills/adversarial-review/SKILL.md frontmatter to match the new version

Commit the version bump:

git commit -am "chore: bump version to X.Y.Z"

Create the version tag: vX.Y.Z

Push commit and tag:

git push origin main
git push origin vX.Y.Z

Confirm completion. Print a summary of:
- Previous version → new version
- Tag created
- Remind the user that the GitHub Actions publish workflow (.github/workflows/publish.yml, triggered on v* tags) will handle the npmjs release automatically.

Mais deste repositório

mesmo repositório

adversarial-review

voodootikigod/adversarial-review

Skeptical ship/no-ship code review of a git diff or branch, run against any LLM (Anthropic / OpenAI / Gemini API, or a local claude / codex / agy CLI). Use before merging or pushing to catch the expensive failure classes a normal review misses: auth and trust-boundary holes, injection, secrets, data loss, rollback safety, race conditions, schema drift, supply-chain and CI/CD changes, test weakening, and observability gaps. Triggers on "review my diff", "review this git diff", "review this branch", "will this break", "is this safe to ship", "adversarial review", "code review before merge", "review before push", "pre-push review", "CI review gate", "ship or no-ship", "find the strongest reason not to ship".

2026-07-216

adversarial-review

voodootikigod/adversarial-review

2026-07-216

name	release
description	Release a new version of adversarial-review (bumps version, tags git, pushes, triggers npm publish)
license	Apache-2.0
user-invocable	true
metadata	{"version":"1.0.0","internal":true}

Release

Use this command to release a new version of adversarial-review.

Arguments

First positional argument: Version bump type — "patch", "minor", or "major". Defaults to "minor" if not specified.

Steps

Determine the new version. Read the current version from package.json. Apply the requested semver bump (default "minor") to compute the new version number.
Verify preconditions:
- Working tree is clean (git status --porcelain is empty)
- On the main branch
- Up to date with remote (git pull --dry-run shows no changes)
- Tests pass (npm test)
Bump version:
- Update the "version" field in package.json
- Update metadata.version in skills/adversarial-review/SKILL.md frontmatter to match the new version

Commit the version bump:

git commit -am "chore: bump version to X.Y.Z"

Create the version tag: vX.Y.Z

Push commit and tag:

git push origin main
git push origin vX.Y.Z

Confirm completion. Print a summary of:
- Previous version → new version
- Tag created
- Remind the user that the GitHub Actions publish workflow (.github/workflows/publish.yml, triggered on v* tags) will handle the npmjs release automatically.