Triage unexpected defects by size and route them to fixes, analysis, or tracked work.
npx skills add https://github.com/jellyrock/jellyrock --skill snag
Please help me install this Agent Skill. Skill: snag Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/snag Command: npx skills add https://github.com/jellyrock/jellyrock --skill snag
When you encounter an unexpected defect, bug, or regression mid-development work, it is tempting to jump straight to a quick first-draft patch that may miss the root cause, introduce new issues, or waste effort on a problem that needs a larger dedicated effort. This skill eliminates that reflex by interposing a triage step between flaw discovery and any fix work.
/log followup or /start-project./snag to get a clear triage and next steps instead of guessing at a patch.Invoke the /snag skill the moment you spot an unexpected defect mid-work to receive a triage of its size and the correct next steps before drafting any fix.
High-intent search queries and answers about installing and using this skill.
Reactive flaw triage interposes a structured step between defect discovery and fix work, rating issues by blast radius to route them to immediate fixes, root-cause analysis with regression verification, or tracked work escalation.
Size-based triage rates defects by blast radius and judgment required into trivial, small/medium, or large categories. Trivial flaws route to zero-ceremony fixes, small/medium to a 5-gate remediation process, and large to tracked work.
Root cause analysis with regression verification is needed for small to medium defects where judgment is required, preventing reflexive patches that miss underlying causes or introduce new issues across cross-cutting shared mechanisms.
Yes, sub-agent delegation is optionally available during the structured 5-gate remediation process for small and medium flaws, specifically assisting with judgment-heavy root cause identification tasks.
Yes, this flaw triage process applies to JellyRock Roku client engineering workflows, handling defects ranging from trivial typos to cross-cutting shared mechanism issues and large multi-session defects.
Large multi-session defects should be escalated to tracked work via dedicated logging or project start commands, ensuring dedicated effort rather than attempting insufficient mid-work patches.
jellyrockGuide registry data migrations for JellyRock Roku app settings.
jellyrockUpdate project plans with git-verified progress and draft next-session handoffs.
leonardoteodorooRun fresh verification commands and validate outputs before claiming completion.
Pepsi1978Automate bugfixing with root-cause analysis, defensive patching, and validation.