🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
πŸ¦€ ClawHub

Senior Dev

by @michaelmonetized

Production development workflow with TODO tracking, Graphite PRs, GitHub issues, Vercel deploy checks, and SMS notifications. Use when starting a new task, fixing bugs, implementing features, or any development work that needs tracked progress and code review.

Versionv0.1.0
Downloads3,672
Installs33
Stars⭐ 5
TERMINAL
clawhub install senior-dev

πŸ“– About This Skill


name: senior-dev description: Production development workflow with TODO tracking, Graphite PRs, GitHub issues, Vercel deploy checks, and SMS notifications. Use when starting a new task, fixing bugs, implementing features, or any development work that needs tracked progress and code review.

Senior Dev

A 12-step production workflow that keeps context across compaction.

Workflow

1. Setup

cd ~/Projects/
Create or append to TODO.md:
## [Date] Task: 
  • [ ] Subtask 1
  • [ ] Subtask 2
  • 2-3. Execute & Track

    Complete work, check off TODO items as done.

    Update CHANGELOG.md (create if missing):

    ## [Unreleased]
    

    Added/Changed/Fixed

  • Description of change
  • 4-5. Stage & Verify

    git add -A
    git diff --staged  # Verify changes match request
    

    6-7. Create PR

    Branch naming: (issue|feature|fix)/

    gt create "feature/add-dark-mode" -m "Add dark mode toggle"
    gt submit
    

    If this fixes an issue, create the issue first:

    gh issue create --title "Bug: description" --body "Details..."
    

    Note the issue number

    gt create "issue/42-fix-login-bug" -m "Fix login bug (#42)" gt submit

    8-9. Review Cycle

    Wait for reviewer comments. Address feedback:
    # Make fixes
    git add -A
    gt modify -m "Address review feedback"
    gt submit
    

    10-11. Post-Merge Deploy Check

    After PR merges:
    git checkout main && git pull
    

    For Vercel projects:

    # Watch deployment (polls until Ready/Error, auto-fetches logs on failure)
    vl
    

    If build fails β†’ gh issue create with error logs, restart from step 6.

    12. Report & Cleanup

    Report completion format: > βœ… [Project] Task completed > PR: > Deploy: success/failed

    Quick Reference

    | Step | Command | Purpose | |------|---------|---------| | Stage | git add -A | Stage all changes | | Verify | git diff --staged | Review before commit | | Branch | gt create "type/name" -m "msg" | Create branch + commit | | PR | gt submit | Push + create/update PR | | Issue | gh issue create | Track bugs/tasks | | Deploy | vl | Watch build, auto-fetch logs on error |

    Branch Prefixes

  • feature/ β€” New functionality
  • fix/ β€” Bug fixes
  • issue/ β€” Linked to GitHub issue (include #number)
  • chore/ β€” Maintenance, deps, config
  • Files to Maintain

  • TODO.md β€” Active task tracking (survives context compaction)
  • CHANGELOG.md β€” Version history
  • PLAN.md β€” Architecture decisions (optional)
  • Tools Required

  • gt β€” Graphite CLI for stacked PRs
  • gh β€” GitHub CLI for issues
  • vl β€” Vercel deploy watcher (or vercel CLI)