Enforce task-driven commits with conventional formats and CLEO task references.
npx skills add https://github.com/kryptobaseddev/cleo --skill ct-dev-workflow
Please help me install this Agent Skill. Skill: ct-dev-workflow Source: https://github.com/kryptobaseddev/cleo/tree/main/skills/ct-dev-workflow Command: npx skills add https://github.com/kryptobaseddev/cleo --skill ct-dev-workflow
This Skill addresses the challenge of enforcing traceable, standardized development work by tying every code change to a CLEO task and ensuring disciplined branching and release-ready workflows.
Focus a task with CLEO, make code changes, stage them, and commit using a conventional format that includes the Task reference. Push to trigger CI and later mark the task complete.
High-intent search queries and answers about installing and using this skill.
To enforce atomic commits tied to task tracking, you map each individual code change to a specific CLEO task using conventional commit formats. This ensures a clear, traceable history where every commit represents a single, isolated unit of work.
Task-driven development is a process tying code changes directly to tracked tasks, integrating with CI workflows via GitHub Actions and CLEO subagents. It enforces required tests and branch restrictions to prevent risky, untracked changes before triggering releases.
Yes, you can use conventional commit formats with GitHub Actions for release preparation by enforcing task-driven gates. This integration standardizes commit messages with task references and automates release readiness checks through CI pipelines.
You set up branch discipline to prevent untracked code changes by applying task-driven gates that require task references and conventional commit formats. This enforces atomic commits and restricts branching to maintain strict traceability across the project.
Yes, the CLEO subagent works with GitHub Actions to automate task completion by streamlining the CI-ready workflow. Pushing code changes triggers CI, which integrates with the subagent to finalize releases and mark the associated tasks complete.
You need task references in conventional commits to enforce traceable, standardized development work in software projects. Tying every code change to a CLEO task ensures disciplined branching and maintains release-ready workflows with clear history.
jamiegrandInitialize cleo-web configuration from a project's .env file.
ccfGenerate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.
aapw01Implement Git workflow best practices and automate CI/CD pipelines with GitHub Actions.
yz0812Analyze Git changes and generate conventional commit messages.
