Categorize implementation issues into fix, note, or leave buckets.
npx skills add https://github.com/gjalla/gjalla-plugin --skill triage-scope
Please help me install this Agent Skill. Skill: triage-scope Source: https://github.com/gjalla/gjalla-plugin/tree/main/claude/skills/triage-scope Command: npx skills add https://github.com/gjalla/gjalla-plugin --skill triage-scope
Triage issues discovered during implementation to decide whether to fix immediately, note for later, or leave alone. This is the "scope filtering" process that senior engineers do continuously while coding: they notice problems that aren't part of the current task and make disciplined decisions about each one.
When you encounter a code-quality issue, apply the three-bucket triage to decide whether to fix now, note for later, or leave alone.
High-intent search queries and answers about installing and using this skill.
Apply a three-bucket triage to categorize each issue as fix now, note for later, or leave alone. This scope filtering process keeps pull requests small and focused by making disciplined decisions about problems outside the current task.
The three-bucket triage method categorizes discovered issues into Fix Now, Note for Later, and Leave Alone. It provides context-driven guidance during code reviews and refactors to systematically assess risk and maintain scope discipline.
Evaluate the risk and scope of the encountered problem against your current task. Apply triage decision-making to fix immediately if critical, note for later if out of scope, or leave alone, documenting each choice for traceability.
Yes, the triage approach applies across code changes, reviews, and refactors. It provides context-driven guidance during all implementation phases to prevent scope creep and ensure code quality issues are consistently categorized.
Avoid this triage strategy when encountering vague or risky problems that require immediate architectural changes, as the bucketing method is designed to maintain scope discipline rather than handle critical, in-flight emergencies.
Document triage decisions during implementation by noting categorized issues for traceability. This aligns with existing workflows, ensuring that items placed in the Note for Later bucket are tracked rather than lost during code changes.
flowgladAutomate pull request reviews using quality, security, and best-practices guidelines.
SSiertsemaPrioritize backlogs with RICE, ICE, Kano, and weighted scoring.
s977043Analyze pull-request diffs to identify security, performance, quality, and test risks.
aniruddh2003Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.
