Agent Skill: hexo-deploy
hexo-deploy
Introduction
This is an Agent Skill for automating Hexo blog site deployment, designed by WaterCoFire specifically for the development workflow of WaterCoFire Playground. It condenses the entire Hexo blog publishing process into a single conversational command, handling all deployment tasks from content generation to code submission.
If you also maintain a Hexo blog site, feel free to use it directly!
Workflow Overview
This Skill splits deployment into two sequential phases:
1 | Phase 1 — Hexo Build & Publish |
If any step fails, the Agent should immediately stop and report the error without proceeding to execute subsequent commands.
How to Use?
Simply tell the Agent you’re using that you want to deploy and provide the commit message:
1 | Deploy for me, commit message is "Added About page" |
The Agent will automatically execute all commands sequentially.
You can also the Agent automatically generate the commit message based on the diff:
1 | Deploy for me, you generate the commit message |
Partial Execution
| Command | Behavior |
|---|---|
Deploy only or Hexo only |
|
Commit only or Git only |
Customization Notes
This Skill is designed under the assumption that: Hexo blog source code is maintained in a separate Git repository (i.e., distinct from the hosting repository pushed by hexo d). This is the repository structure of WaterCoFire Playground.
If your setup differs, please adjust accordingly before use:
Single Git repository (source code = hosting repository)
Remove the Git phase in Phase 2, or integrate it into the hexo d logic.
No need for hexo clean
Remove this command from Phase 1.
Main branch is not main
Replace main in git push origin main with your branch name.
Prerequisites
- Hexo CLI is installed and configured (
hexocommand is available) - Deployment target for
hexo dis correctly configured in_config.yml - Git is initialized, remote repository
originis set up
File Contents
Metadata
1 | --- |
Full File
Click the button below to download.
