[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSGAPRE52W5KM5D96WY5B4":3,"skill-same:01M7CSGAPRE52W5KM5D96WY5B4":48},{"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":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CSGAPRE52W5KM5D96WY5B4","error-definitions",null,"Use before proposing error definitions (propose_error_definitions) - how to read an error group, pick its category and action, write a match that catches one kind of error and nothing else, and when a definition should not be proposed at all","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Frelease-engineer\u002Fskills\u002Ferror-definitions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: error-definitions\ncategory: observability\ndescription: Use before proposing error definitions (propose_error_definitions) - how to read an error group, pick its category and action, write a match that catches one kind of error and nothing else, and when a definition should not be proposed at all\n---\n\n# Error definitions\n\nAn error definition says what one kind of runtime error means and what happens when it recurs. A person accepts or dismisses each one you propose, so every proposal has to stand on its own: a name a person recognises, a match they can read, a category and action they would have chosen, and a one-sentence rationale.\n\n## Category: what it is\n\n| Category | It is | Usual action |\n|---|---|---|\n| `bug` | this code does the wrong thing (a nil dereference, an unhandled case, a wrong query) | `task` — one developer task per new group; `incident` if it breaks a core flow |\n| `expected` | a designed outcome logged at error level (a cancelled checkout, a webhook for an unknown event, a cache miss logged loudly) | `ignore`, or `none` to keep it visible but labelled |\n| `user_error` | input the code rejects correctly (validation, not found, unauthorised, rate limited) | `ignore` unless a sudden rise would mean an attack or a broken client — then `alert` with a threshold |\n| `dependency` | a downstream service or API failing (timeouts, 5xx from a provider, a broker disconnect) | `alert` with a threshold: one timeout is noise, fifty in ten minutes is an outage |\n| `infrastructure` | the platform itself (out of memory, disk full, DNS, the database refusing connections) | `incident` |\n\nRead the code before you choose: the line that raises it, and what its callers do with it. A `404` the API returns on purpose is `user_error`; a `404` the service gets back from its own storage is a `bug` or a `dependency`.\n\n## Match: one kind of error, nothing else\n\nEvery field you set must hold.\n\n- `fingerprint` — exactly one group. Use it when the group is one specific failure and its message would match too much.\n- `message_regex` — a family. Anchor on the words that never change (`^payment provider timeout`), escape what is literal (`\\(`, `\\.`), and never include an id, a timestamp, an amount or a host that varies between occurrences. Test it mentally against two different groups of the family.\n- `exception_type` — the class or error type as printed before the first `:`; a bare name (`TimeoutError`) matches its qualified form.\n- `endpoint` (`POST \u002Fv1\u002Fcharges`, `\u002Fv1\u002Forders\u002F*`) and `status` (`504`) — when the message prints them, to tell the same exception on two routes apart.\n- `attributes` — exact `key=value` pairs the message prints (`tenant=acme`), or `source` \u002F `provider`.\n\nA match that also catches unrelated groups is worse than none: an `ignore` hides real failures and an `alert` pages for the wrong thing. When in doubt, narrow it.\n\n## Thresholds\n\nFor `alert` and `incident`, set `alert_threshold` from what the group does today: its `count` over a window in `list_error_groups`. A dependency that times out three times an hour normally wants an alert at, say, twenty in ten minutes — not at one. Leave it out and the defaults apply (alert: 10 in an hour; incident: any occurrence).\n\n## Severity\n\n`critical` only when a core flow is down for everyone; `high` when users notice; `medium` for degraded but working; `low` for noise you still want counted.\n\n## Evidence and rationale\n\n`evidence`: the group fingerprints it matches and the `file:line` that raises it. `rationale`: one sentence a person reads in the Errors page before accepting — \"Raised in payments\u002Fclient.go:88 when the provider exceeds 5 s; retried once, so a burst means the provider is down.\"\n\n## Do not propose\n\n- A group you could not trace to code — say in your reply that it is unexplained instead.\n- A definition for a group that already carries one (`definition` is set in `list_error_groups`).\n- Anything whose only purpose is to make the inbox look empty. `ignore` is for errors that are genuinely expected, never for defects nobody has fixed yet.\n","# Error definitions\n\nAn error definition says what one kind of runtime error means and what happens when it recurs. A person accepts or dismisses each one you propose, so every proposal has to stand on its own: a name a person recognises, a match they can read, a category and action they would have chosen, and a one-sentence rationale.\n\n## Category: what it is\n\n| Category | It is | Usual action |\n|---|---|---|\n| `bug` | this code does the wrong thing (a nil dereference, an unhandled case, a wrong query) | `task` — one developer task per new group; `incident` if it breaks a core flow |\n| `expected` | a designed outcome logged at error level (a cancelled checkout, a webhook for an unknown event, a cache miss logged loudly) | `ignore`, or `none` to keep it visible but labelled |\n| `user_error` | input the code rejects correctly (validation, not found, unauthorised, rate limited) | `ignore` unless a sudden rise would mean an attack or a broken client — then `alert` with a threshold |\n| `dependency` | a downstream service or API failing (timeouts, 5xx from a provider, a broker disconnect) | `alert` with a threshold: one timeout is noise, fifty in ten minutes is an outage |\n| `infrastructure` | the platform itself (out of memory, disk full, DNS, the database refusing connections) | `incident` |\n\nRead the code before you choose: the line that raises it, and what its callers do with it. A `404` the API returns on purpose is `user_error`; a `404` the service gets back from its own storage is a `bug` or a `dependency`.\n\n## Match: one kind of error, nothing else\n\nEvery field you set must hold.\n\n- `fingerprint` — exactly one group. Use it when the group is one specific failure and its message would match too much.\n- `message_regex` — a family. Anchor on the words that never change (`^payment provider timeout`), escape what is literal (`\\(`, `\\.`), and never include an id, a timestamp, an amount or a host that varies between occurrences. Test it mentally against two different groups of the family.\n- `exception_type` — the class or error type as printed before the first `:`; a bare name (`TimeoutError`) matches its qualified form.\n- `endpoint` (`POST \u002Fv1\u002Fcharges`, `\u002Fv1\u002Forders\u002F*`) and `status` (`504`) — when the message prints them, to tell the same exception on two routes apart.\n- `attributes` — exact `key=value` pairs the message prints (`tenant=acme`), or `source` \u002F `provider`.\n\nA match that also catches unrelated groups is worse than none: an `ignore` hides real failures and an `alert` pages for the wrong thing. When in doubt, narrow it.\n\n## Thresholds\n\nFor `alert` and `incident`, set `alert_threshold` from what the group does today: its `count` over a window in `list_error_groups`. A dependency that times out three times an hour normally wants an alert at, say, twenty in ten minutes — not at one. Leave it out and the defaults apply (alert: 10 in an hour; incident: any occurrence).\n\n## Severity\n\n`critical` only when a core flow is down for everyone; `high` when users notice; `medium` for degraded but working; `low` for noise you still want counted.\n\n## Evidence and rationale\n\n`evidence`: the group fingerprints it matches and the `file:line` that raises it. `rationale`: one sentence a person reads in the Errors page before accepting — \"Raised in payments\u002Fclient.go:88 when the provider exceeds 5 s; retried once, so a burst means the provider is down.\"\n\n## Do not propose\n\n- A group you could not trace to code — say in your reply that it is unexplained instead.\n- A definition for a group that already carries one (`definition` is set in `list_error_groups`).\n- Anything whose only purpose is to make the inbox look empty. `ignore` is for errors that are genuinely expected, never for defects nobody has fixed yet.\n",{"name":5,"category":24,"description":7},"observability","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Frelease-engineer\u002Fskills\u002Ferror-definitions",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill error-definitions",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill error-definitions",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill error-definitions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Frelease-engineer\u002Fskills\u002Ferror-definitions\u002FSKILL.md",true,[],[49,55,62,69,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":6,"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},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\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":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]