[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EQ7GR4ZZ6E75VY4YV3PZKB":3,"skill-same:01M7EQ7GR4ZZ6E75VY4YV3PZKB":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EQ7GR4ZZ6E75VY4YV3PZKB","issue-triage",null,"Triaging error reports — prioritization, ownership, and keeping the backlog actionable — works with any error tracker.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-issue-triage\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: issue-triage\ndescription: Triaging error reports — prioritization, ownership, and keeping the backlog actionable — works with any error tracker.\ncategory: sentry\n---\n\n## Overview\n\nAn error tracker without triage becomes a write-only database of sadness:\nthousands of open issues, nobody looking. Triage is the discipline of\nregularly reviewing new errors, assigning ownership, and keeping the backlog\na true reflection of product health. This skill covers the process.\n\n## When to use\n\n- Setting up a triage rotation or process for error reports\n- Prioritizing which errors to fix first (frequency × severity)\n- Defining ownership of errors across teams\u002Fservices\n- Reducing a massive untriaged backlog to something manageable\n- Deciding when to ignore, mute, or archive error issues\n\n## Core concepts\n\n**Triage is a cadence, not an event.** 15–30 minutes daily (or a few times\nweekly) reviewing new\u002Funresolved issues beats quarterly \"error bankruptcy\"\nsessions. Small, frequent, owned — like inbox zero for production errors.\n\n**Prioritize by impact: frequency × severity × trend.** A crash affecting\n10% of sessions outranks a rare edge-case warning. Rising trends outrank\nstable ones (something changed). New issues from the latest release outrank\nold known issues (possible regression). Build the priority order from these,\nnot from gut feel.\n\n**Every issue needs a state and an owner.** States: new (untriaged),\ntriaged\u002Fassigned, in progress, resolved, archived\u002Fignored (with a reason).\nOwner = the team\u002Fservice that owns the code path. Unowned issues rot; route\nby service ownership mapping (which team owns which stack frames\u002Fpaths).\n\n**Not every error deserves a fix.** Some errors are external (user's network,\nbrowser extensions, bots), some are acceptable (validated input rejected\ncorrectly — though that might be a UX signal), some are duplicates. It's\nfine to archive with a documented reason — what's not fine is leaving them\n\"new\" forever, which hides real problems in noise.\n\n**Regressions get fast-tracked.** A previously resolved issue reappearing —\nespecially right after a deploy — is the highest-priority class: it means a\nfix was reverted or a deploy reintroduced a bug. Alert on regressions\nspecifically and investigate immediately.\n\n## Practical workflow\n\n1. **Set the cadence:** daily 15-min triage (rotating owner or per-team),\n   with a slightly deeper weekly review of trends and the backlog.\n2. **Work the queue:** for each new issue — reproduce\u002Fassess impact, check\n   if it's a regression, assign owner + priority, or archive with reason.\n   Don't leave anything \"new\" past the triage session.\n3. **Attack the backlog systematically:** sort by frequency, work top-down\n   in batches; bulk-archive the provably-harmless with documented reasons;\n   set a target (e.g. zero untriaged, \u003C50 open) and track it.\n4. **Maintain ownership mapping:** service → team, kept current as code\n   moves; auto-assign where the tracker supports rules.\n5. **Track metrics:** new issues per release, mean time to triage, % of\n   issues resolved vs archived, top issues by user impact — trends tell you\n   whether quality is improving.\n6. **Feed back into prevention:** recurring error classes → better\n   validation, better types, better tests; the triage notes are a roadmap\n   for reliability work.\n\n## Common pitfalls\n\n- **No cadence** — triage \"when someone has time\" means never; schedule it\n  like any other operational duty.\n- **Everything is P1** — without real prioritization, nothing is; use\n  impact-based ordering ruthlessly.\n- **Orphan issues** — no owner, no state changes, aging silently; ownership\n  mapping is non-optional.\n- **Deleting instead of archiving with reason** — the same error returns\n  next month and nobody remembers why it was dismissed; reasons are\n  documentation.\n- **Fixing symptoms in triage** — triage assigns and prioritizes; the fix\n  happens in normal engineering workflow (sprint, not the triage meeting).\n- **Ignoring trends** — individual issues look small, but a 5x rise in a\n  category signals a systemic problem; watch the aggregates, not just the\n  items.\n","## Overview\n\nAn error tracker without triage becomes a write-only database of sadness:\nthousands of open issues, nobody looking. Triage is the discipline of\nregularly reviewing new errors, assigning ownership, and keeping the backlog\na true reflection of product health. This skill covers the process.\n\n## When to use\n\n- Setting up a triage rotation or process for error reports\n- Prioritizing which errors to fix first (frequency × severity)\n- Defining ownership of errors across teams\u002Fservices\n- Reducing a massive untriaged backlog to something manageable\n- Deciding when to ignore, mute, or archive error issues\n\n## Core concepts\n\n**Triage is a cadence, not an event.** 15–30 minutes daily (or a few times\nweekly) reviewing new\u002Funresolved issues beats quarterly \"error bankruptcy\"\nsessions. Small, frequent, owned — like inbox zero for production errors.\n\n**Prioritize by impact: frequency × severity × trend.** A crash affecting\n10% of sessions outranks a rare edge-case warning. Rising trends outrank\nstable ones (something changed). New issues from the latest release outrank\nold known issues (possible regression). Build the priority order from these,\nnot from gut feel.\n\n**Every issue needs a state and an owner.** States: new (untriaged),\ntriaged\u002Fassigned, in progress, resolved, archived\u002Fignored (with a reason).\nOwner = the team\u002Fservice that owns the code path. Unowned issues rot; route\nby service ownership mapping (which team owns which stack frames\u002Fpaths).\n\n**Not every error deserves a fix.** Some errors are external (user's network,\nbrowser extensions, bots), some are acceptable (validated input rejected\ncorrectly — though that might be a UX signal), some are duplicates. It's\nfine to archive with a documented reason — what's not fine is leaving them\n\"new\" forever, which hides real problems in noise.\n\n**Regressions get fast-tracked.** A previously resolved issue reappearing —\nespecially right after a deploy — is the highest-priority class: it means a\nfix was reverted or a deploy reintroduced a bug. Alert on regressions\nspecifically and investigate immediately.\n\n## Practical workflow\n\n1. **Set the cadence:** daily 15-min triage (rotating owner or per-team),\n   with a slightly deeper weekly review of trends and the backlog.\n2. **Work the queue:** for each new issue — reproduce\u002Fassess impact, check\n   if it's a regression, assign owner + priority, or archive with reason.\n   Don't leave anything \"new\" past the triage session.\n3. **Attack the backlog systematically:** sort by frequency, work top-down\n   in batches; bulk-archive the provably-harmless with documented reasons;\n   set a target (e.g. zero untriaged, \u003C50 open) and track it.\n4. **Maintain ownership mapping:** service → team, kept current as code\n   moves; auto-assign where the tracker supports rules.\n5. **Track metrics:** new issues per release, mean time to triage, % of\n   issues resolved vs archived, top issues by user impact — trends tell you\n   whether quality is improving.\n6. **Feed back into prevention:** recurring error classes → better\n   validation, better types, better tests; the triage notes are a roadmap\n   for reliability work.\n\n## Common pitfalls\n\n- **No cadence** — triage \"when someone has time\" means never; schedule it\n  like any other operational duty.\n- **Everything is P1** — without real prioritization, nothing is; use\n  impact-based ordering ruthlessly.\n- **Orphan issues** — no owner, no state changes, aging silently; ownership\n  mapping is non-optional.\n- **Deleting instead of archiving with reason** — the same error returns\n  next month and nobody remembers why it was dismissed; reasons are\n  documentation.\n- **Fixing symptoms in triage** — triage assigns and prioritizes; the fix\n  happens in normal engineering workflow (sprint, not the triage meeting).\n- **Ignoring trends** — individual issues look small, but a 5x rise in a\n  category signals a systemic problem; watch the aggregates, not just the\n  items.\n",{"name":5,"category":24,"description":7},"sentry","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-issue-triage",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill issue-triage",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill issue-triage",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill issue-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-issue-triage\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]