Automate Git lifecycle workflows from feature branches to production deployment.
npx skills add https://github.com/earayu/treadstone --skill dev-lifecycle-earayu
Please help me install this Agent Skill. Skill: dev-lifecycle Source: https://github.com/earayu/treadstone/tree/main/.agents/skills/dev-lifecycle Command: npx skills add https://github.com/earayu/treadstone --skill dev-lifecycle-earayu
This guide provides a governance-backed, repeatable lifecycle for developing, reviewing, and releasing code within Treadstone, ensuring changes pass through feature branches, pull requests, CI validation, and controlled production deployment instead of direct merges to main.
Follow the documented lifecycle steps to create a feature branch, open a PR, run CI, merge, bump version, and deploy to production.
High-intent search queries and answers about installing and using this skill.
You can automate a Git development lifecycle by enforcing feature branch creation, PR openings, CI validation, and controlled production deployment. This workflow prevents direct pushes to main and standardizes ship, bump, release, merge, and deploy steps.
The best way to prevent direct pushes to main is implementing a governance-backed lifecycle where all changes land via Pull Requests. This requires CI checks to pass before merging, ensuring controlled production deployment.
To trigger a version bump and deploy after merging a pull request, follow the standardized release lifecycle steps. This workflow coordinates the merge, automates the version bump, applies release tagging, and executes the optional production deploy.
Yes, this Git release workflow supports CI validation and release tagging for team coordination. It provides an agent-facing lifecycle that standardizes ship, bump, release, merge, and deploy-all actions using GitHub feature branches.
Yes, you can use this pull request workflow to coordinate feature branch development and production deployment. It provides explicit guidance for branch creation, PR opening, CI checks, merging, version bumping, and final deployment.
You should avoid direct merges to main in a CI-driven GitHub workflow whenever shipping code. All changes must pass through feature branches and pull requests to ensure CI validation and controlled release governance before reaching production.
Nabilhassan12345Create a GitHub pull request from the active branch with guided prompts.
SjdjdiejdrirhdkjejPromote validated staging builds to production with semantic versioning and health checks.
quan0715Enforce branch, commit, PR, and release rules for GitHub repositories.
DonNigamiAutomate GitHub repository governance and CI/CD workflows with GitHub Actions.
