start-task

Repository locks signal active work and prevent simultaneous task conflicts. Start Task acquires a lock for your specific repository and task, blocking other developers from starting work until the lock is released, ensuring clean, conflict-free development.

Start Task verifies your working directory is clean before beginning any coding work. It confirms no uncommitted changes exist, then checks out the correct branch or creates a new one, protecting you from accidental commits or merge conflicts.

Start Task manages branch creation and checkout automatically. Specify your base branch, and the Skill creates a new task-specific branch from master or another base, records task metadata, and prepares your environment for immediate coding.

Yes. Start Task exposes a status command to verify lock status before attempting to start a new task. It reports whether the repository is locked by another task, letting you coordinate with teammates or wait until work is complete.

No. Start Task records task metadata automatically during initialization. It captures task context as you acquire the repository lock, eliminating manual logging and ensuring consistent task tracking across your firmware and configurator projects.

Start Task enforces a clean working directory requirement and will not proceed. You must commit or stash any uncommitted changes first. This precaution prevents accidental data loss and ensures every task begins from a known, reproducible state.