Validate repository state and tests, then deploy code over SSH with health checks.
npx skills add https://github.com/SalesTeamToolbox/frood --skill deploy-salesteamtoolbox
Please help me install this Agent Skill. Skill: deploy Source: https://github.com/SalesTeamToolbox/frood/tree/main/.claude/skills/deploy Command: npx skills add https://github.com/SalesTeamToolbox/frood --skill deploy-salesteamtoolbox
This Skill prevents risky, broken, or poorly-tested deployments by enforcing pre-flight checks, controlled Git workflow, and a post-deploy health verification step.
Ask the Skill to run the full deploy workflow for frood, starting with the mandatory pre-flight checks and ending with production health verification.
High-intent search queries and answers about installing and using this skill.
Automating a safe git deployment workflow requires enforcing a clean working tree, running pytest, executing a controlled git push and merge into main, deploying via SSH, and verifying the production service health endpoint returns HTTP 200. This prevents risky deployments by validating repository state and test results before restarting the service.
Blocking deployments when the git working tree is dirty or tests fail is handled by pre-flight guardrails. These checks stop the pipeline if there are no commits to deploy, if the working tree is unclean, or if the pytest suite fails, with limited allowances for known pre-existing failures.
A continuous deployment pipeline verifies a production service restart over SSH by confirming the service is active and checking that the health endpoint returns an HTTP 200 response. This operational verification happens after the controlled git merge and service restart.
Deploying code to a production server when pytest has known pre-existing failures is possible with limited allowances. The deployment pipeline blocks failing test suites but can bypass specific known failures, ensuring new code changes do not introduce untested regressions before the SSH deployment.
Your deployment fails when there are no new commits to push from dev to main because the pre-flight guardrails require commit-ahead logic. The pipeline blocks execution if there is nothing to deploy, ensuring only meaningful changes are merged and pushed to the production server.
saadjsConvert uncommitted changes into small conventional commits via git add -p.
mr-daedaliumMerge PRs, trigger deployment, and verify canary health in CI/CD pipelines.
sleepinginsummerExecute commands and transfer files on remote servers via SSH.
Jia-Hong-PengMerges pull requests and verifies production canary health after CI/CD deployment completes.
