# Snipsnap Do Chores

> Work through saved mechanical improvements when the user says "snipsnap do chores."

- Skill: `sreejithraman/snipsnap-do-chores` (Agent Skill)
- Install (CLI): `npx get-skill add sreejithraman/snipsnap-do-chores`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sreejithraman/snipsnap-do-chores/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: sreejithraman (https://skillmd.com/u/sreejithraman)
- Updated: 2026-11-16
- Page: https://skillmd.com/skills/sreejithraman/snipsnap-do-chores

---


# Snip Snap chores

Chores are maintenance tasks with an established, verifiable outcome: removing
dead code, reducing duplication, correcting stale docs, or fixing a confirmed
bug against existing requirements. Leave features and unresolved product
decisions open, including those discovered during work.

Use [Snip Snap](../snip-snap/SKILL.md) to find ready, unfinished chores for the
current project. Read each candidate and its completion evidence so finished
work stays out of the selection, including work recorded only in older notes.

Use [Implement](../implement/SKILL.md) for chores forming one outcome,
or [Coordinator](../coordinator/SKILL.md) to coordinate several outcomes.
Use [Swarm](../swarm/SKILL.md) when bounded parallel work helps the caller.
Carry each source snip's ID in execution briefs and handoffs. Follow
Snip Snap's [Complete saved work](../snip-snap/SKILL.md#complete-saved-work)
rules throughout execution and completion.

When delivering chores as PRs, freely choose one PR, multiple independent PRs,
or a stack for dependent changes, based on what keeps review clear. Use
[PR](../pr/SKILL.md) for delivery and [gh-stack](../gh-stack/SKILL.md) for stacks.

