Publishing

Verified changes reach users as copied skill bundles (via npm run build and npx skills add), Claude plugin marketplace artifacts, and the GitHub Pages documentation site. There is no hosted RedTeam runtime to deploy.

Artifacts and destinations

Artifact	Destination	Versioned by	Owner
Skill source	`skills/redteam/` in repo	Git commit / npm package files field	Maintainers
Provider bundles	`.cursor/`, `.claude/`, `.agents/`, `.github/`, `.gemini/`, `plugin/`	Git commit after `npm run build`	Maintainers
`dist/` tarball layout	`dist/` via `npm run build:dist`	Git tag / release	Maintainers
Skill install	`npx skills add DecisionNerd/RedTeam`	GitHub default branch; `npx skills update` pulls latest	Maintainers
Claude plugin	`.claude-plugin/` marketplace manifest	Git commit	Maintainers
Documentation site	GitHub Pages `https://decisionnerd.github.io/RedTeam/`	`main` branch deploy	Maintainers

Build and continuous delivery

npm run build          # copy skill to provider directories
npm run sync           # propagate package.json version/owner, then build
npm run build:dist     # dist/ only
npm run docs:site      # stage docs, astro check, build, link check
npm test

docs:site and npm test must pass before merging doc or skill changes. Provider copies should be rebuilt with npm run build when skills/redteam/ changes.

Versioning

package.json is the single source of truth for the version and the GitHub owner/repo.

npm version patch      # or minor | major
git push --follow-tags

preversion runs npm test. version runs npm run sync, which rewrites plugin manifests, skill frontmatter, config templates, documentation URLs, and provider copies, then stages them so one commit carries the bump. Push manually.

To change the repository owner, edit repository.url in package.json, run npm run sync, and commit.

Environments and promotion

From	To	Required evidence / approval
Feature branch	`main`	PR review; local `npm test` and `docs:site` for affected areas
`main`	GitHub Pages	CI `deploy.yml` — `npm run docs:site` must succeed
`main` / tag	`npx skills add` consumers	GitHub repo availability; users pull latest on install
`main`	Claude plugin users	Marketplace sync after manifest/skill changes

Deployment verification

Docs: npm run docs:site completes; scripts/check-docs-site.mjs validates /RedTeam/ links
Install: REDTEAM_E2E=1 npm test runs a real npx skills add into a temp project; plain npm test is the offline check of the source skill, provider copies, init scaffold, and metadata
Harness: maintainer spot-checks /redteam challenge after skill changes

Rollback and recovery

Docs site: revert commit on main and let CI redeploy, or roll back GitHub Pages deployment
Skill content: revert Git commit; users reinstall or pull latest
No production database or stateful service — rollback is content revert only