Senior Dev
VerifiedProduction 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.
$ Add to .claude/skills/ About This Skill
# Senior Dev
A 12-step production workflow that keeps context across compaction.
Workflow
1. Setup ```bash cd ~/Projects/<project> ``` Create or append to `TODO.md`: ```markdown ## [Date] Task: <description> - [ ] Subtask 1 - [ ] Subtask 2 ```
2-3. Execute & Track Complete work, check off TODO items as done.
- Update `CHANGELOG.md` (create if missing):
- ```markdown
- ## [Unreleased]
- ### Added/Changed/Fixed
- Description of change
- ```
4-5. Stage & Verify ```bash git add -A git diff --staged # Verify changes match request ```
6-7. Create PR Branch naming: `(issue|feature|fix)/<short-description>`
```bash gt create "feature/add-dark-mode" -m "Add dark mode toggle" gt submit ```
If this fixes an issue, create the issue first: ```bash 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: ```bash # Make fixes git add -A gt modify -m "Address review feedback" gt submit ```
10-11. Post-Merge Deploy Check After PR merges: ```bash git checkout main && git pull ```
For Vercel projects: ```bash # 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: <url> > 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)
Use Cases
- Generate structured output from specifications or requirements
- Create structured plans with milestones, timelines, and deliverables
- Deploy applications and services to production environments
- Track and analyze personal metrics for health and productivity insights
- Integrate Senior Dev into existing development and automation workflows
Pros & Cons
Pros
- +Well-adopted with 1,857+ downloads showing reliable real-world usage
- +Clean CLI interface integrates well with automation pipelines and AI agents
- +Automates infrastructure operations for consistency and reliability
- +Reduces manual intervention in deployment and maintenance workflows
Cons
- -Requires specific infrastructure setup and tool dependencies
- -Configuration errors in infrastructure tools can have production impact
FAQ
What does Senior Dev do?
What platforms support Senior Dev?
What are the use cases for Senior Dev?
100+ free AI tools
Writing, PDF, image, and developer tools — all in your browser.
Next Step
Use the skill detail page to evaluate fit and install steps. For a direct browser workflow, move into a focused tool route instead of staying in broader support surfaces.