Senior Dev
Production development workflow with TODO tracking, Graphite PRs, GitHub issues, Vercel deploy checks, and SMS notifications. Use when starting a new task, fixing bugs, implementin…
michaelmonetized
@michaelmonetized
Install
$ openclaw skills install @michaelmonetized/senior-devSenior Dev
A 12-step production workflow that keeps context across compaction.
Workflow
1. Setup
cd ~/Projects/<project>
Create or append to TODO.md:
## [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):
## [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)/<short-description>
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: <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 functionalityfix/— Bug fixesissue/— 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 PRsgh— GitHub CLI for issuesvl— Vercel deploy watcher (orvercelCLI)
Related skills
Web Deploy GitHub Pages
@thomeksolutionsCreate and deploy single-page static websites to GitHub Pages with autonomous workflow. Use when building portfolio sites, CV pages, landing pages, or any static web project that needs GitHub Pages deployment. Handles complete workflow from project initialization to live deployment with GitHub Actions automation.
Requesting Code Review
@zlc000190Use when completing tasks, implementing major features, or before merging to verify work meets requirements
GitHub
@byungkyuGitHub API integration with managed OAuth. Access repositories, issues, pull requests, commits, branches, and users. Use this skill when users want to interact with GitHub repositories, manage issues and PRs, search code, or automate workflows. For other third party apps, use the api-gateway skill (
Code Review
@wpankSystematic code review patterns covering security, performance, maintainability, correctness, and testing — with severity levels, structured feedback guidance, review process, and anti-patterns to avoid. Use when reviewing PRs, establishing review standards, or improving review quality.
Github
@steipeteInteract with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
GitHub
@hith3shWork with GitHub repositories, issues, pull requests, commits, branches, releases, and workflows via the GitHub REST and GraphQL APIs. Use this skill when us...