How does this skill handle branch naming?

It uses a standardized pattern, typically 'feature/{issue-number}-{sanitized-description}', ensuring consistency and traceability across your repository.

Can it fix my development environment automatically?

Yes, it can be configured to auto-start Docker services and run pending database migrations if it detects they are not ready.

Where is the session configuration stored?

Configuration and session state are managed in a .task_wrapup_skill_data.json file in your project root, which is shared with the task-wrapup skill.

Do I need the GitHub CLI installed to use this skill?

Yes, for the GitHub integration features like fetching issues, you must have the GitHub CLI (gh) installed and authenticated on your machine.

Development Task Orchestrator

Name: Development Task Orchestrator
Author: arlenagreer

byarlenagreer

Productivity & Workflow

Automates development work session initialization by validating environments, fetching GitHub issues, and creating standardized feature branches.

About

The Task-Start skill streamlines the developer workflow by managing the repetitive boilerplate required to start new tasks. It performs comprehensive preflight git checks, verifies the health of Docker containers and databases, and integrates directly with GitHub to load issue context. By automatically creating properly formatted branches and initializing session state, it ensures your development environment is fully prepared and compliant with project standards before you write a single line of code.

Key Features

Seamless GitHub Issue integration for fetching task descriptions and priorities
Session state logging to facilitate automated pull request creation
Automated Git preflight checks to prevent work on protected branches
0 GitHub stars
Standardized branch naming conventions (e.g., feature/123-description)
Environment health validation for Docker, databases, and dependencies

Use Cases

Automating the transition from a GitHub issue to a local development branch
Initializing a clean development environment for a new feature or bug fix
Enforcing consistent team-wide branch naming and environment setup standards

About

Key Features

Seamless GitHub Issue integration for fetching task descriptions and priorities
Session state logging to facilitate automated pull request creation
Automated Git preflight checks to prevent work on protected branches
0 GitHub stars
Standardized branch naming conventions (e.g., feature/123-description)
Environment health validation for Docker, databases, and dependencies

Use Cases

Automating the transition from a GitHub issue to a local development branch
Initializing a clean development environment for a new feature or bug fix
Enforcing consistent team-wide branch naming and environment setup standards