← ClaudeAtlas

workflowlisted

Daily development workflow reference. Quick-start guides for solo dev, team collaboration, production launches, and emergency hotfixes. Points to detailed steps in supporting files.
buildproven/claude-kit · ★ 0 · AI & Automation · score 65
Install: claude install-skill buildproven/claude-kit
# Workflow Skill — Daily Development Guide Quick reference for all development workflows. Read `daily-steps.md` for detailed command sequences. ## Quick Start ```bash /bs:dev "feature name" # Start work — creates a worktree, never edits on main # ... code ... /bs:quality --merge # Ship it — runs review, merges PR, returns to main, removes worktree /clear # Fresh context ``` ## Worktree Discipline (NON-NEGOTIABLE) The primary checkout is **inspection-only**. Never edit, commit, or stage on the primary checkout's `main` branch. Every piece of work happens in a linked worktree on a feature branch. ```bash # Create a canonical worktree (preferred — `/bs:dev` does this for you) node scripts/worktree-manager.js create \ --repo /path/to/repo --branch <type>/<slug> \ --creator manual --purpose "<task>" # Inspect lifecycle state or reconcile after a manual/admin merge node scripts/worktree-manager.js status --repo /path/to/repo node scripts/worktree-manager.js reconcile --repo /path/to/repo --apply ``` Worktrees live at `<primary-repo-parent>/.worktrees/<repo-name>/<branch-slug>`, outside the repository so recursive searches, linters, secret scans, IDEs, and backups do not accidentally traverse another checkout. Resolution always starts from the primary checkout's Git common directory, even when invoked in a linked worktree. `/bs:quality --merge` MUST handle the cleanup tail. If you ever find yourself with uncommitted changes on the primary che