nsheaps/deploy
plugins/sdlc-utils/skills/deploy/SKILL.md
Deployment and release management. Use when the user asks about "deployment", "CI/CD", "release", "shipping", "publishing", "deploy pipeline", "release process", or when setting up or managing deployment workflows. Covers CI/CD configuration, release strategies, and deployment validation.
$ install --global
skillsauthnpx skillsauth add nsheaps/ai-mktpl deployInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 4:16 PM57.8s1 file scanned
SKILL.md
- name:
- deploy
- description:
- >
Deployment
Guidelines for deploying and releasing software.
Workflow
Step 1: Pre-Deployment Checklist
Before deploying:
- [ ] All tests pass in CI
- [ ] Code review approved
- [ ] No known blocking issues
- [ ] Deployment plan documented (if non-trivial)
- [ ] Rollback strategy identified
Step 2: CI/CD Pipeline
- CI should be easily reproducible locally using the same source of truth
- CI failures are considered validation failures regardless of local results
- Pipelines should be fast — parallelize independent steps
- Keep pipeline configuration DRY (reusable workflows/actions)
Step 3: Release Strategy
Choose appropriate strategy for the change:
| Strategy | When to use | | ------------- | ------------------------------------ | | Rolling | Low-risk changes, stateless services | | Blue-green | Need instant rollback capability | | Canary | High-risk changes, gradual rollout | | Feature flags | Decoupling deploy from release |
Step 4: Post-Deployment Validation
After deploying:
- Run smoke tests against the deployed environment
- Monitor error rates and key metrics
- Verify the change works as expected in production
- Keep rollback ready for a defined period
Anti-Patterns
| Anti-Pattern | Instead | | ------------------ | --------------------------------------- | | Manual deployments | Automate with CI/CD | | No rollback plan | Always have a rollback strategy | | Skipping staging | Validate in a staging environment first | | Big-bang releases | Deploy incrementally | | Deploy on Friday | Deploy when you can monitor the result |
Related Skills
nsheaps/github-app-session-env
tools
VerifiedTrustedCommunity
Manually reproduce what the github-app plugin's SessionStart hook does to make a GitHub App installation token usable in the current session — materialize the PEM, generate the token, isolate GH_CONFIG_DIR, write the runtime env file, and wire CLAUDE_ENV_FILE so every Bash call sees GH_TOKEN/GITHUB_TOKEN. Use when the hook did not run, the token is missing from the environment, or a shell/teammate needs the token wired up by hand. <example>GH_TOKEN isn't set even though github-app is configured</example> <example>the github-app SessionStart hook didn't run, set up the token manually</example> <example>wire the github app token into CLAUDE_ENV_FILE</example> <example>gh keeps falling back to the wrong account, isolate GH_CONFIG_DIR</example>
3SKILL.mdUpdated Jun 9, 2026
nsheaps/github-app-git-identity
tools
VerifiedTrustedCommunity
Manually configure the GitHub App bot git identity the way the github-app plugin's SessionStart hook does — resolve the app slug and bot user ID, build the <slug>[bot] name and noreply email, set GIT_AUTHOR_*/GIT_COMMITTER_* env vars, and write an isolated GIT_CONFIG_GLOBAL with the gh auth git-credential helper. Use when commits are attributed to the wrong account, "Author identity unknown" appears, or git identity must be set up by hand. <example>my commits are showing up as the handler, not the bot</example> <example>git says Author identity unknown after the github-app hook ran</example> <example>configure the github app bot git identity manually</example> <example>set up the gh credential helper for git push</example>
3SKILL.mdUpdated Jun 9, 2026
nsheaps/spec-management
tools
VerifiedTrustedCommunity
Manages spec files for requirements capture and validation
3SKILL.mdUpdated Jun 7, 2026
nsheaps/plugins/bash-command-rejection/skills/bash-chaining-alternatives
tools
VerifiedTrustedCommunity
# Bash Chaining Alternatives This skill teaches you how to work around the bash command chaining restriction enforced by this plugin. ## Why Chaining is Blocked The `bash-command-rejection` plugin blocks these operators: | Operator | Name | Why Blocked | | -------- | ---------- | ----------------------------------------------------------------------------------- | | `&&` | AND chain | Runs cmd2 only if cmd1 su
3SKILL.mdUpdated Jun 7, 2026