quick-deploy

Build, upload via FTP, and validate front-end releases.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/zhu637882-stack/jiaoyi --skill quick-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-deploy
Source: https://github.com/zhu637882-stack/jiaoyi/tree/main/qoder-config-backup/skills/quick-deploy
Command: npx skills add https://github.com/zhu637882-stack/jiaoyi --skill quick-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

快速部署前端应用,减少人工重复操作,自动化构建、上传和上线验证。

Core Features & Use Cases

  • 自动构建前端:一键完成代码构建,输出可部署产物。
  • FTP 上传与部署验证:将产物上传到服务器并执行上线检查,确保版本一致性。
  • 回滚与版本控制:遇到问题时快速回滚到上一个版本,确保稳定性。

Quick Start

在确认环境配置后,直接触发“部署前端”以完成从构建到上线的全流程。

Frequently Asked Questions about quick-deploy

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

FAQPage Schema
How do I automate frontend deployment with FTP upload and verification?

Automating frontend deployment involves building the code, uploading artifacts via FTP, and running post-deploy checks to validate live releases. This process ensures repeatable deployments with rollback support and status reporting across web apps.

What is the best way to perform a rollback after a failed frontend deployment?

A rollback after a failed frontend deployment reverts the application to the previous stable version. Automated deployment workflows include rollback capabilities to quickly restore stability when post-deploy verification detects version inconsistencies or errors.

Can I use configurable build commands for my frontend web app deployment?

Configurable build commands are supported for frontend web app deployment. You can define custom build commands, FTP targets, and automated verification steps within your deployment configuration to match your project requirements.

Does automated FTP deployment include post-deploy checks for live releases?

Automated FTP deployment includes post-deploy checks for live releases. After uploading build artifacts to the server, the system executes automated verification steps to ensure version consistency and validate the live release.

Why do I need automated verification steps in my frontend deployment process?

Automated verification steps are needed in frontend deployment to ensure version consistency after uploading artifacts. They validate the live release by checking the deployed output against expected results, reducing manual checks and human error.