ct-dev-workflow

Development workflow orchestration for task-driven development with atomic commits, conventional commit messages, and systematic release processes. Enforces task traceability, branch discipline, smart test scope selection, and GitHub Actions integration. Use when committing code, creating releases, managing branches, or following contribution protocols. Triggers on commit operations, release preparation, or workflow compliance needs.

Aller à l'installation

Dépôt: kryptobaseddev/cleo
Dernière activité de la source: 22 avril 2026 à 16:31
Langue détectée de SKILL.md: anglais
Étoiles: 160
Forks: 21

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/kryptobaseddev/cleo --skill ct-dev-workflow

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

ct-task-executor

General implementation task execution for completing assigned CLEO tasks by following instructions and producing concrete deliverables. Handles coding, configuration, documentation work with quality verification against acceptance criteria and progress reporting. Use when executing implementation tasks, completing assigned work, or producing task deliverables. Triggers on implementation tasks, general execution needs, or task completion work.

2026-08-20

ct-orchestrator

Pipeline-aware orchestration skill for managing complex workflows through subagent delegation. Use when the user asks to "orchestrate", "orchestrator mode", "run as orchestrator", "delegate to subagents", "coordinate agents", "spawn subagents", "multi-agent workflow", "context-protected workflow", "agent farm", "HITL orchestration", "pipeline management", or needs to manage complex workflows by delegating work to subagents while protecting the main context window. Enforces ORC-001 through ORC-009 constraints. Provider-neutral — works with any AI agent runtime.

2026-06-30

skill-monorepo

CLEO provider adapter for Anthropic Claude Code CLI. Default export is the adapter class for dynamic loading by AdapterManager. T5240 Use when: (1) calling its 2515 API functions, (2) configuring @cleocode/monorepo, (3) understanding its 1754 type definitions, (4) working with its 104 classes, (5) user mentions "@cleocode/monorepo" or asks about its API.

2026-06-03

Tout voir dans ce dépôt

name	ct-dev-workflow
description	Development workflow orchestration for task-driven development with atomic commits, conventional commit messages, and systematic release processes. Enforces task traceability, branch discipline, smart test scope selection, and GitHub Actions integration. Use when committing code, creating releases, managing branches, or following contribution protocols. Triggers on commit operations, release preparation, or workflow compliance needs.
version	3.0.0
tier	2
core	false
category	specialist
protocol	contribution
dependencies	[]
sharedResources	["subagent-protocol-base","task-system-integration"]
compatibility	["claude-code","cursor","windsurf","gemini-cli"]
license	MIT

Development Workflow Context Injection

Protocol: @src/protocols/contribution.md Type: Context Injection (cleo-subagent) Version: 3.0.0

Purpose

Context injection for development workflow tasks spawned via cleo-subagent. Provides domain expertise for atomic commits with task traceability, conventional commit messages, and systematic release processes.

Core Principle: Task-Driven Development

CRITICAL: NO code changes or commits without a tracked task.

Every commit MUST be traceable to a CLEO task. This ensures:

Work is planned and tracked
Changes are reviewable and reversible
Progress is measurable
Context is preserved for future agents

Immutable Constraints (WORKFLOW)

ID	Rule	Enforcement
WF-001	Task required	NO commits without CLEO task reference
WF-002	Branch discipline	NO commits to main/master
WF-003	Atomic commits	ONE logical change per commit
WF-004	Conventional format	`<type>(<scope>): <description>`
WF-005	Tests before push	Relevant tests MUST pass

Task Tracking Integration

Before Any Work

# 1. Verify you have a task
cleo current

# 2. If no task, find or create one
cleo find "relevant query"
cleo add "Task title" --description "What you're doing" --parent T001
cleo start T123

Commit Message Format

MUST include task reference:

<type>(<scope>): <description>

<body explaining why>

Task: T123
Co-Authored-By: Claude <noreply@anthropic.com>

Example:

fix(auth): prevent token expiry race condition

The refresh token was being invalidated before the new access
token was validated, causing intermittent auth failures.

Task: T1456
Co-Authored-By: Claude <noreply@anthropic.com>

Type	Description	Tests Needed	Version Bump
`feat`	New feature	Related tests	MINOR
`fix`	Bug fix	Regression test	PATCH
`docs`	Documentation	None	None
`refactor`	Code restructure	Affected tests	PATCH
`test`	Test additions	The new tests	None
`chore`	Maintenance	None	None
`perf`	Performance	Perf tests	PATCH
`security`	Security fix	Security tests	PATCH

Change Type	Test Scope	Command
`feat`	Related module tests	`bats tests/unit/feature.bats`
`fix`	Regression + affected	`bats tests/unit/affected.bats`
`docs`	None (CI validates)	Skip
`refactor`	Affected modules	`bats tests/unit/module*.bats`
`test`	The new tests only	`bats tests/unit/new.bats`
`chore`	Syntax check only	`bash -n scripts/*.sh`

Change	Local Tests	Rely on CI
Single file fix	Related unit test	Yes
New feature	Feature tests	Yes
Docs only	None	Yes
Schema change	Schema tests	Yes
Cross-cutting refactor	Full suite	Yes
Release prep	Full suite	Yes

Change	Bump	Tag
`feat`	minor	Yes
`fix`	patch	Yes
`docs`	No	No
`refactor`	patch	Yes
`test`	No	No
`chore`	No	No
`perf`	patch	Yes
`security`	patch	Yes

Pattern	Problem	Solution
No task reference	Untracked work	Create/find task first
Committing to main	Bypass review	Use feature branches
Running full tests always	Slow iteration	Use smart test scope
Skipping CI	Missing validations	Always push, let CI run
Manual release creation	Inconsistent releases	Use tag, GH Actions
Giant commits	Hard to review/revert	Atomic commits
Vague commit messages	Lost context	Conventional + task ref

ct-dev-workflow

Options d'installation

Vérifiez les fichiers source

Development Workflow Context Injection

Purpose

Core Principle: Task-Driven Development

Immutable Constraints (WORKFLOW)

Task Tracking Integration

Before Any Work

Commit Message Format

Development Workflow Context Injection

Purpose

Core Principle: Task-Driven Development

Immutable Constraints (WORKFLOW)

Task Tracking Integration

Before Any Work

Commit Message Format

Branch & Subagent Awareness

Single Branch Reality

Branch Strategy

Gate System (Simplified)

G0: Pre-Flight Check

G1: Classify Change

G2: Testing (Smart Scope)

G3: Commit

G4: Push (Triggers CI)

G5: Version Bump (Release Only)

G6: Tag & Release

Quick Decision Matrix

What Tests to Run?

Do I Need a Version Bump?

Task System Integration

CLEO Integration Commands

Subagent Protocol

Output Requirements

Complete Workflow Examples

Example 1: Bug Fix (Typical)

Example 2: Documentation Only

Anti-Patterns

Critical Rules Summary

ct-dev-workflow

Informations de source

Options d'installation

Vérifiez les fichiers source

Plus depuis ce dépôt

Plus depuis ce dépôt

Development Workflow Context Injection

Purpose

Core Principle: Task-Driven Development

Immutable Constraints (WORKFLOW)

Task Tracking Integration

Before Any Work

Commit Message Format

Development Workflow Context Injection

Purpose

Core Principle: Task-Driven Development

Immutable Constraints (WORKFLOW)

Task Tracking Integration

Before Any Work

Commit Message Format

Branch & Subagent Awareness

Single Branch Reality

Branch Strategy

Gate System (Simplified)

G0: Pre-Flight Check

G1: Classify Change

G2: Testing (Smart Scope)

G3: Commit

G4: Push (Triggers CI)

G5: Version Bump (Release Only)

G6: Tag & Release

Quick Decision Matrix

What Tests to Run?

Do I Need a Version Bump?

Task System Integration

CLEO Integration Commands

Subagent Protocol

Output Requirements

Complete Workflow Examples

Example 1: Bug Fix (Typical)

Example 2: Documentation Only

Anti-Patterns

Critical Rules Summary