lucastosetto/dev-skills

Claude Code skills for the whole engineering loop, from reading a ticket to watching it in
production. They work in any repo: each project's issue tracker, PR host, deploy method, feature
flags and observability are discovered once and cached in a profile outside the repo.
Install
Or inside Claude Code: /plugin marketplace add lucastosetto/dev-skills, then /plugin install dev-skills.
Skills
| Skill | What it does |
|---|---|
| implement | Ticket → worktree → spec + QA plan → code → verify → docs → local commit → push/PR (confirmed) |
| investigate | Read-only root cause with logs, metrics, traces and data; drafts the ticket and support reply |
| pr-review | Critical-only review against the linked ticket; re-review checks follow-up rounds |
| address-comments | Works through review comments on your PR: fixes valid ones, short replies, resolves bot threads |
| prs-follow-up | For each of your open PRs in every repo: updates the branch, resolves conflicts, addresses comments, fixes failed checks |
| deploy | staging or prod: changelog, deploy, read-only smoke test, monitoring, rollback |
| todo | One numbered report of what needs you: today's tickets from the day plan with real PR status, reviews for you, your PRs, unanswered Slack (managers, DMs, mentions, support; last 24h) and comments; builds missing plans, replan to redo them |
| sprint | Day-by-day sprint plan over business days; today: the day plan, built once a day |
| standup | Short bullet update since the last daily from commits, PRs, reviews, tickets and sessions |
| demo | Presentation-friendly walkthrough of an implementation |
| spec | Implementation spec, or rfc for a structured RFC |
| qa-plan | Automated (unit/integration/E2E) and manual QA plan |
| qa | Runs checks and acceptance criteria; boots the app and drives it for real |
| gather-context | Reads tickets, docs and threads; maps code, criteria, unknowns, blockers |
| observe | Health of a feature or deploy vs a baseline |
| document | Updates the project's API docs (OpenAPI, Postman, README) and gives curl examples |
| resolve-conflicts | Judgment-based git conflict resolution with a report |
| project-profile | Discovers and caches the project's setup; holds your notes |
Commands are prefixed: /dev-skills:implement PROJ-123.
Autonomy modes
| Mode | Asks before |
|---|---|
| autonomous | Only actions that leave your machine or change shared data |
| balanced (default) | The above, plus commits, out-of-plan changes, new dependencies, migrations, deletions, behavior-changing conflicts |
| guided | The above, plus approving the spec and QA plan and choosing between approaches |
Push, PRs, comments, tickets, messages, deploys, flags and shared-data writes are confirmed in every
mode, collected into one list at the end of the run. Production deploys and rollbacks are always
confirmed.
Switch with /dev-skills:mode (this session), /dev-skills:mode project or
/dev-skills:mode global, or add the mode to a single request: /dev-skills:implement PROJ-123 guided.