The nitpin Skill

The nitpin skill runs inside your coding agent, in a repo wired up with nitpin init (or a global nitpin install). It’s how the agent turns captures into fixes, and it responds to plain language as readily as to slash commands.

Fix the backlog — /nitpin

Type /nitpin with no arguments — or just say “check nitpin”, “any new issues?”, or “fix the QA feedback”. The agent:

1. Triages if needed — only when the backlog was never triaged or has drifted enough to warrant it.
2. Picks one cluster (or one closely-related issue) and claims it.
3. Looks at the screenshots — the focused crops of what each pin points at, your notes, and the discussion thread (your replies count as instruction).
4. Finds the code and fixes it, one sub-issue at a time, resolving each with a note and the commit.
5. Stops when that one logical chunk is done and summarizes.

One logical thing per session is the default, on purpose: each change stays focused and reviewable.

Triage only — /nitpin triage

Organizes the backlog without fixing anything. See Running Triage.

Fix everything — /nitpin fix everything

Clears the whole open backlog, still one cluster at a time: triage first if needed, walk the clusters in priority order, then the ungrouped issues — batching the small stuff efficiently — and finish with a closing tally: what was fixed, what was declined and why, what was skipped, and any questions left in threads.

Fix a tag — /nitpin fix #ios

Fixes only the open issues carrying a tag you wrote in your notes (#ios, #dark-mode, #checkout). Say it naturally — “fix the #ios issues” works too.

Fix a specific bug

Reference an issue or sub-issue by number and the agent jumps straight to it: “fix issue #3”, “what’s sub-issue 2 on issue 5?”.

Binding

The skill acts on the project bound to the repo it’s running in: the .nitpin/ store inside the repo, or the project linked via nitpin link. If nothing is bound, the agent stops and asks which project to use rather than guessing; nitpin init or nitpin link fixes that permanently.