deployment

Automates deployment configuration, publishing, and log-based diagnostics for web apps.

18|4|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/El3tar-cmd/DevHive-Cli --skill deployment-el3tar-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment
Source: https://github.com/El3tar-cmd/DevHive-Cli/tree/main/skills/deployment
Command: npx skills add https://github.com/El3tar-cmd/DevHive-Cli --skill deployment-el3tar-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Configures deployment settings, publishes your project, and helps you diagnose and fix production issues across environments.

Core Features & Use Cases

  • Verify and replace an artifact's deployment configuration via verifyAndReplaceArtifactToml to safely update run/build commands without editing files directly.
  • Schedule and announce deployment readiness with suggestDeploy, guiding users through the publishing flow from the main repl context.
  • Fetch and analyze deployment logs with fetchDeploymentLogs to diagnose runtime errors and monitor health.
  • Understand and choose deployment targets autoscale, vm, scheduled, and static to match your app's needs.
  • Locate deployment configuration in PNPM workspaces (artifact.toml inside .replit-artifact) and keep .replit untouched, with artifact settings controlling run/build steps.
  • Access reference materials like references/deployment-logs.md for in-depth guidance.

Quick Start

Update the artifact configuration with verifyAndReplaceArtifactToml and then trigger publishing with suggestDeploy when ready.

Frequently Asked Questions about deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure deployment targets for a PNPM workspace project?

To configure deployment targets for a PNPM workspace, you update the artifact.toml file located inside the .replit-artifact directory. This file controls your run and build steps without modifying the .replit file, allowing you to select targets like autoscale, vm, scheduled, or static.

How do I fetch deployment logs to debug production runtime errors?

You can fetch deployment logs to debug production runtime errors using the fetchDeploymentLogs workflow. This diagnostic function retrieves health data and runtime logs from deployed environments to help identify and resolve issues quickly.

What is the best way to update run and build commands without editing project files directly?

The best way to update run and build commands without editing files directly is to use the verifyAndReplaceArtifactToml function. This method safely verifies and replaces your deployment configuration within the artifact.toml file to ensure correct run and build steps.

Can I use artifact.toml to manage production-ready deployments for web apps?

Yes, you can use artifact.toml to manage production-ready deployments for web apps and services. The configuration supports artifact.toml based run and build commands across multiple deployment targets including autoscale, vm, scheduled, and static environments.

How do I trigger publishing and announce deployment readiness from my main repl context?

You trigger publishing and announce deployment readiness by using the suggestDeploy function. This guides you through the publishing flow directly from your main repl context to safely schedule and announce your production rollout.

Why should I keep the .replit file untouched when configuring deployment settings?

You should keep the .replit file untouched because deployment settings are managed separately within the .replit-artifact directory. Locating deployment configuration in artifact.toml ensures your run and build steps remain isolated, reducing manual setup errors and downtime.