agentleFS
Asno-devAsno-dev/apex/skills/deploy-pipeline/SKILL.md

deploy-pipeline

Skill1 starsChanged 5 months agoMITView on GitHub

Invoke when setting up deployment, CI/CD, or automation pipeline. "deploy this", "set up CI", "automate this workflow", "ship this", "GitHub Actions", "deployment pipeline", "CI/CD". SDLC categories: Software Development, Software Maintenance. Terminal-Bench class — autonomous multi-step CLI workflows.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-deep-links, helium-mcp 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.
  • ComposioHQSkill

    agent-deep-links

    Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.

    Also in 3 projects that use this

  • ComposioHQSkill

    helium-mcp

    Search real-time news with bias scoring, get live stock/ETF/crypto data with AI analysis, ML options pricing, balanced news synthesis, and meme search via the Helium MCP server.

    Also in 3 projects that use this

  • petestewartSkill

    datadog-logs

    Query Datadog logs via the Logs Search API v2. Use when the user asks to "check the logs", "search logs", "find errors in Datadog", "look up logs for", "show me production logs", "check for errors", "search Datadog", or any request involving log search, error investigation, or production debugging that requires Datadog log data.

    Also in 3 projects that use this

  • OpenAISkill

    notion-meeting-intelligence

    Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

    Also in 3 projects that use this

  • +8 more from ComposioHQ

The file

Files
SKILL.md

Deploy Pipeline Protocol (Io's Protocol)

  1. ENVIRONMENT MAP — dev → staging → production. Each: what runs, config, access
  2. CI PIPELINE — install → typecheck → lint → test → build → deploy Fail fast (cheapest first). Cache by lockfile hash. Secrets via CI-native store. Branch protection: main requires passing CI
  3. DEPLOY STRATEGY
    • Rolling update for stateless services
    • Blue-green for stateful/zero-downtime
    • DB migrations: before code deploy, never after
  4. OBSERVABILITY
    • Structured JSON logging
    • Health endpoint: GET /health → {status, version, uptime}
    • Alert on: error rate >1%, p99 >500ms, memory >80%
  5. ROLLBACK — Every deploy includes tested rollback path

Output: Working config files. Zero prose. Deploy + rollback commands.

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.