agentsclimarketplace

Deployment automation

Skill qodex-ai/ai-agent-skills/skills/deployment-automation

Automate deployment to Vercel platform. Manages deployment configuration, environment setup, and CI/CD integration.From its SKILL.md

Install
npx -y skills add qodex-ai/ai-agent-skills --skill deployment-automation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its file declares

Copied from the file, not written here

The file declares its own license as Proprietary. LICENSE.txt has complete terms. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, as published. Nobody here has run it

Vercel Production Deploy Loop

Instructions

When requested to deploy to Vercel production with automatic error fixing:

  1. Initial Deployment Attempt

    • Run vercel --prod to start production deployment
    • Wait for deployment to complete
  2. Error Detection & Analysis

    • CRITICAL: Use Vercel MCP tool to fetch detailed logs:
      • The MCP logs provide much more detail than CLI output
    • Analyze the build logs to identify root cause:
      • Build errors (TypeScript, ESLint, compilation)
      • Runtime errors
      • Environment variable issues
      • Dependency problems
      • Configuration issues
    • Extract specific error messages
  3. Error Fixing

    • Make minimal, targeted fixes to resolve the specific error
  4. Retry Deployment

    • Run vercel --prod again with the fixes applied
    • Repeat steps until deployment succeeds
  5. Success Confirmation

    • Once deployment succeeds, report:
      • Deployment URL
      • All errors that were fixed
      • Summary of changes made
    • Ask if user wants to commit/push the fixes

Loop Exit Conditions

  • ✅ Deployment succeeds
  • ❌ SAME error occurs 5+ times (suggest manual intervention)
  • ❌ User requests to stop

Best Practices

  • Make incremental fixes rather than large refactors
  • Preserve user's code style and patterns when fixing

Example Flow

User: "Deploy to production and fix any errors"

  • Vercel MCP build logs are the PRIMARY source of error information
  • CLI output alone is insufficient for proper error diagnosis
  • Always wait for deployment to complete before fetching logs
  • If errors require user input (like API keys), prompt user immediately

Keep looking

Skills are one crate of 615,528. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.