Verify git branch, HEAD SHA, commit sync, and clean working tree before deployment.
npx skills add https://github.com/Dragoon0x/dragoon-skills --skill land-dragoon0x
Please help me install this Agent Skill. Skill: land Source: https://github.com/Dragoon0x/dragoon-skills/tree/main/skills/land Command: npx skills add https://github.com/Dragoon0x/dragoon-skills --skill land-dragoon0x
This Skill eliminates the risk of broken production deployments caused by out-of-sync local and remote git repositories, uncommitted working tree changes, or incorrect branch selection before a deploy step.
Use the land skill to verify your repository is fully synced and clean before triggering a production deploy.
High-intent search queries and answers about installing and using this skill.
A pre-deploy check validates your git repository by confirming the current branch, verifying local commits match the remote, and ensuring the working tree has no uncommitted changes before a production deploy. It prevents broken deployments caused by out-of-sync states.
A working tree check verifies that no uncommitted modifications exist in your local repository. You need it before pushing to production because uncommitted changes can cause incomplete or broken deployments if they are not properly committed and synced with the remote.
Yes, you can integrate pre-push validation as a CI pipeline step run immediately before invoking platform-specific deploy commands. It confirms local-remote commit sync and validates branch selection without triggering any actual deploy actions.
Local-remote commit sync verification confirms that local commits match the remote repository with no unpushed or unpulled changes. It ensures the code being deployed is fully synchronized and complete across both repositories.
No, this pre-deploy git validation tool does not trigger any deployment actions. It serves strictly as a lightweight validation layer that performs sanity checks and reports repository status before you manually invoke your deploy commands.
Deploying with unpushed commits or an out-of-sync git repository causes broken or incomplete production deployments. Running a sanity check first catches these discrepancies by verifying your HEAD SHA and local-remote sync status.
dyoshikawaAnalyze git differences and commit history between the current branch and origin main.
sun2443Generate a pre-deployment checklist with deploy, post-deploy, and rollback sections.
luissimon96Automate the mcp-graph DEPLOY phase with DORA metric and CI pipeline checks.
open-haxCheck git branch, working tree, remotes, and submodules before destructive operations.
