agentleFS
KhaiTrang1995KhaiTrang1995/claude-code-structure/.claude/skills/deploy/SKILL.md

deploy

Skill1 starsChanged 7 months agoMITView on GitHub

161 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pm-discovery, qa-phase and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ww-w-aiSkill

    pm-discovery

    PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.

    Also in 3 projects that use this

  • ww-w-aiSkill

    qa-phase

    Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans.

    Also in 3 projects that use this

  • +10 more from ww-w-ai

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 142 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All tests passing: npm test

    line 13
  2. Very specific:

    No lint errors: npm run lint

    line 14
  3. Very specific:

    Check service health endpoint: GET /api/health

    line 28

“Common” is measured: kept by at least 6 in 10 of the 142 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deploy Skill

Trigger Context

This skill activates automatically when the task involves:

  • Deploying to staging or production
  • CI/CD pipeline configuration
  • Docker / container builds
  • Cloud provider (AWS, GCP, Azure) operations

Workflow

Pre-deploy Checklist

  1. All tests passing: npm test
  2. No lint errors: npm run lint
  3. Environment variables set for target environment
  4. Database migrations reviewed

Deploy Steps

# Build production artifact
npm run build

# Run deploy script (see deploy-config.md for environment vars)
./scripts/deploy.sh --env production

Post-deploy Verification

  • Check service health endpoint: GET /api/health
  • Review application logs for errors
  • Smoke test critical user flows

Rollback

./scripts/deploy.sh --rollback --env production

References

  • Environment-specific config: .claude/skills/deploy/deploy-config.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.