michaelmonetized

Senior Dev

Developmentv0.1.0
By michaelmonetizedUpdated 2026-05-11senior-dev@clawhub_michaelmonetized/senior-dev
ScriptingGit#Code Review#Deploy#GitHub

According to AlphaMoat, as of 2026-09, Senior Dev has 4,348 downloads and 5 stars — ranked #2,260 of 5,078 AI skills overall, and #284 of 577 in Development.

Installs
144
Downloads
4.3K
Stars
5
Overall Rank
#2,260
Top 45% overall · Top 50% in Development
PlatformInstallsDownloadsStarsComments
ClawHub ↗1444.3K5-
SkillHub ↗1424.3K5—

Platforms count differently and update at different times.

What this skill does

The workflow tracks progress with a task list and recommends maintaining a changelog; later steps may stage repository files, create issues or PRs, and check deployments. Before repository or external actions, define the task scope and obtain confirmation. Stage only files related to the task, and review and redact logs before creating issues. The documented workflow uses Graphite and GitHub CLIs; deployment checking depends on the project's tools.

Profile published 2026-10-29

What you can do with it

  • Track TODO items and progress for feature work or bug fixes
  • Organize code-review and deployment-check steps for a change
  • Prepare a structured task-completion report

When to use it

  • When the task scope, repository, and expected deliverables are clear
  • When file changes can be reviewed and staging can be limited to task-specific files
  • When explicit confirmation can be obtained before creating PRs, issues, or triggering deployment

Example prompts

Generated from the skill’s documentation as examples; not results of actual runs.

List TODO, verification, and review steps for a scoped bug fix. Do not run Git, Graphite, GitHub, or deployment commands.

Monthly Trend

Downloads4.3K
2.8K3.6K4.5K2026-03 · Downloads 2.9K2026-05 · Downloads 3.7K2026-06 · Downloads 3.8K2026-07 · Downloads 4.1K2026-08 · Downloads 4.2K2026-09 · Downloads 4.3K26-0326-09
Stars5
4552026-03 · Stars 42026-05 · Stars 52026-06 · Stars 52026-07 · Stars 52026-08 · Stars 52026-09 · Stars 526-0326-09

The counting method changed in 2026-09: skills with the same name are now counted separately by author, and the full catalog is covered. Dashed lines show months before the change; they are not compared with later months, and no growth is computed across the change.

MonthDownloadsMoMStars
2026-094.3K—5
2026-084.2K+2.9%5
2026-074.1K+6.8%5
2026-063.8K+4.0%5
2026-053.7K—5
2026-032.9K—4

SKILL.md (original)

The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 2026-10-23.

2.7 KB · ClawHub v0.1.0
---
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
Show all (113 lines)

### 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](https://graphite.dev) for stacked PRs
- `gh` — [GitHub CLI](https://cli.github.com) for issues
- `vl` — Vercel deploy watcher (or `vercel` CLI)

Popular in Development

More from michaelmonetized

Data month: 2026-09 · Downloads, stars and installs are aggregated monthly from public skill registries (ClawHub, SkillHub). See methodology.