Surfaces team conventions for shipping code whenever the user is — or is about to be — writing, testing, reviewing, deploying, or operating production code. Activate on user intent, not just slash commands. Fire when the user is writing new code in an existing repo (style, lint, conventions apply); adding or updating tests; preparing a pull request (review process, required checks, branch rules); modifying CI/CD workflows or GitHub Actions; editing Terraform / Pulumi / other IaC; configuring deploys (Heroku, Cloud Run, GCP, staging, prod); touching repo settings managed centrally (branch protection, rulesets, collaborators, autolinks); configuring DNS (DNSimple) or CDN (Fastly); running or debugging tests; releasing or rolling back; configuring observability or alerting; setting up secrets or environment configuration. Conversational shapes that should trigger include "let me add tests for X", "is this ready to merge", "how do we deploy Y", "set up CI for this service", "add a github actions workflow", "configure branch protection", "should I use [tool] for tests", "what's our convention for [code pattern]", "how do we handle migrations", "where does this terraform go", "create a state bucket", "should I deploy to Heroku", "add a fastly rule", "what's our lint config", "how do we name PRs". Also fires on slash invocations like /review, /ship, /plan, /test, /refactor when the work is shipping-shaped. Reads the team's SHIPPING.md and interjects only when there's a specific convention or process to flag for the current context. Stays silent if tstack isn't configured, SHIPPING.md is missing, or no relevant guidance applies.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryEngineeringStars0
About this skill
Surfaces team conventions for shipping code whenever the user is — or is about to be — writing, testing, reviewing, deploying, or operating production code. Activate on user intent, not just slash commands. Fire when the user is writing new code in an existing repo (style, lint, conventions apply); adding or updating tests; preparing a pull request (review process, required checks, branch rules); modifying CI/CD workflows or GitHub Actions; editing Terraform / Pulumi / other IaC; configuring deploys (Heroku, Cloud Run, GCP, staging, prod); touching repo settings managed centrally (branch protection, rulesets, collaborators, autolinks); configuring DNS (DNSimple) or CDN (Fastly); running or debugging tests; releasing or rolling back; configuring observability or alerting; setting up secrets or environment configuration. Conversational shapes that should trigger include "let me add tests for X", "is this ready to merge", "how do we deploy Y", "set up CI for this service", "add a github actions workflow", "configure branch protection", "should I use [tool] for tests", "what's our convention for [code pattern]", "how do we handle migrations", "where does this terraform go", "create a state bucket", "should I deploy to Heroku", "add a fastly rule", "what's our lint config", "how do we name PRs". Also fires on slash invocations like /review, /ship, /plan, /test, /refactor when the work is shipping-shaped. Reads the team's SHIPPING.md and interjects only when there's a specific convention or process to flag for the current context. Stays silent if tstack isn't configured, SHIPPING.md is missing, or no relevant guidance applies.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Surfaces team conventions for shipping code whenever the user is — or is about to be — writing, testing, reviewing, deploying, or operating production code. Activate on user intent, not just slash commands. Fire when the user is writing new code in an existing repo (style, lint, conventions apply); adding or updating tests; preparing a pull request (review process, required checks, branch rules); modifying CI/CD workflows or GitHub Actions; editing Terraform / Pulumi / other IaC; configuring deploys (Heroku, Cloud Run, GCP, staging, prod); touching repo settings managed centrally (branch protection, rulesets, collaborators, autolinks); configuring DNS (DNSimple) or CDN (Fastly); running or debugging tests; releasing or rolling back; configuring observability or alerting; setting up secrets or environment configuration. Conversational shapes that should trigger include "let me add tests for X", "is this ready to merge", "how do we deploy Y", "set up CI for this service", "add a github actions workflow", "configure branch protection", "should I use [tool] for tests", "what's our convention for [code pattern]", "how do we handle migrations", "where does this terraform go", "create a state bucket", "should I deploy to Heroku", "add a fastly rule", "what's our lint config", "how do we name PRs". Also fires on slash invocations like /review, /ship, /plan, /test, /refactor when the work is shipping-shaped. Reads the team's SHIPPING.md and interjects only when there's a specific convention or process to flag for the current context. Stays silent if tstack isn't configured, SHIPPING.md is missing, or no relevant guidance applies.
About this listing
Category
Engineering
Reported license
Apache-2.0
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI