Claude Skills by dimitritholen

Land a tasqx task's branch on protected main without waiting on it — push, open the PR, arm auto-merge (rebase, without --delete-branch) and move on to the next task; at the next task boundary check the PR, send failed checks or real Qodo findings back to a builder, and once it is MERGED reinstall, verify, clean up and close the task once. Use it when a task's branch has passed review under CLAUDE.md's "One task, one branch" rule, or when the user asks to land, merge, ship or open the PR for ...

Retrospective on the tasqx tasks completed in this session — review the decisions and rework that got them done, record the lessons on each task, and decide whether a procedure earns a skill. Use at the end of a session, or when the user says retro, retrospective, post-mortem, lessons learned, or asks what we learned. Never triggered by completing a task.

Use tasqx (MCP tools + CLI) for backlogs, task tracking and knowledge memory. Use it whenever the user starts or continues feature work, wants work planned or tracked, asks what is open or what to pick up next, wants a status report, or wants a decision or convention stored or looked up — even when they never say "tasqx". Skip it for one-off questions and one-line fixes.