[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P820ZG8Z221W6DD2TDC9YN":3,"skill-same:01M6P820ZG8Z221W6DD2TDC9YN":100},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":14,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6P820ZG8Z221W6DD2TDC9YN","frontend-code-review",null,"Review pending frontend changes or specific frontend files against code-quality, performance, and business-logic checklists. USE FOR: \"review a React component diff\", \"review pending .tsx changes\", \"review only a .tsx file\". DO NOT USE FOR: creating new React components or implementing changes without a review request.","sarthchawla\u002FSetupMyAI","sarthchawla","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F41484686?v=4","01M6P7D22NFMY9MA11Q2YGPKV2","Sarthak Chawla","01M6P7D26JJ9KW98SD1G8BB83R",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Freact-frontend\u002Fskills\u002Ffrontend-code-review\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"frontend","review","code review","frontend code review","code","pending","for","implementing","do","files","tsx","only","diff","use","business","file","react components","react","components","performance","2026-11-10 10:12:30",false,"---\nname: frontend-code-review\ndescription: 'Review pending frontend changes or specific frontend files against code-quality, performance, and business-logic checklists. USE FOR: \"review a React component diff\", \"review pending .tsx changes\", \"review only a .tsx file\". DO NOT USE FOR: creating new React components or implementing changes without a review request.'\n---\n\n# Frontend Code Review\n\n## Intent\nUse this skill whenever the user asks to review frontend code (especially `.tsx`, `.ts`, or `.js` files). Support two review modes:\n\n1. **Pending-change review** -- inspect staged\u002Fworking-tree files slated for commit and flag checklist violations before submission.\n2. **File-targeted review** -- review the specific file(s) the user names and report the relevant checklist findings.\n\nStick to the checklist below for every applicable file and mode.\n\n## Checklist\nLoad `review-adjudication` to verify claims and counterevidence before suggesting or applying fixes; keep this review read-only unless edits are authorized.\n\nWhen changed tests claim reset behavior, supplied-prop effects, scrolling, or absence of an asynchronous request, read [scenario reachability](references\u002Fscenario-reachability.md).\n\nWhen a reusable package's published peer contract or packaging transform changes, read [published peer contracts](references\u002Fpublished-peer-contract.md).\nSee [references\u002Fcode-quality.md](references\u002Fcode-quality.md), [references\u002Fperformance.md](references\u002Fperformance.md), [references\u002Fbusiness-logic.md](references\u002Fbusiness-logic.md) for the living checklist split by category -- treat it as the canonical set of rules to follow.\n\nFlag each rule violation with urgency metadata so future reviewers can prioritize fixes.\n\n## Review Process\n1. Open the relevant component\u002Fmodule. Gather lines that relate to class names, React Flow hooks, prop memoization, and styling.\n2. For each rule in the review point, note where the code deviates and capture a representative snippet.\n3. Compose the review section per the template below. Group violations first by **Urgent** flag, then by category order (Code Quality, Performance, Business Logic).\n\n## Required output\nWhen invoked, the response must exactly follow one of the two templates:\n\n### Template A (any findings)\n```\n# Code review\nFound \u003CN> urgent issues need to be fixed:\n\n## 1 \u003Cbrief description of bug>\nFilePath: \u003Cpath> line \u003Cline>\n\u003Crelevant code snippet or pointer>\n\n\n### Suggested fix\n\u003Cbrief description of suggested fix>\n\n---\n... (repeat for each urgent issue) ...\n\nFound \u003CM> suggestions for improvement:\n\n## 1 \u003Cbrief description of suggestion>\nFilePath: \u003Cpath> line \u003Cline>\n\u003Crelevant code snippet or pointer>\n\n\n### Suggested fix\n\u003Cbrief description of suggested fix>\n\n---\n\n... (repeat for each suggestion) ...\n```\n\nIf there are no urgent issues, omit that section. If there are no suggestions, omit that section.\n\nIf the issue number is more than 10, summarize as \"10+ urgent issues\" or \"10+ suggestions\" and just output the first 10 issues.\n\nDon't compress the blank lines between sections; keep them as-is for readability.\n\nIf you use Template A (i.e., there are issues to fix) and at least one issue requires code changes, append a brief follow-up question after the structured output asking whether the user wants you to apply the suggested fix(es). For example: \"Would you like me to use the Suggested fix section to address these issues?\"\n\n### Template B (no issues)\n```\n## Code review\nNo issues found.\n```\n","# Frontend Code Review\n\n## Intent\nUse this skill whenever the user asks to review frontend code (especially `.tsx`, `.ts`, or `.js` files). Support two review modes:\n\n1. **Pending-change review** -- inspect staged\u002Fworking-tree files slated for commit and flag checklist violations before submission.\n2. **File-targeted review** -- review the specific file(s) the user names and report the relevant checklist findings.\n\nStick to the checklist below for every applicable file and mode.\n\n## Checklist\nLoad `review-adjudication` to verify claims and counterevidence before suggesting or applying fixes; keep this review read-only unless edits are authorized.\n\nWhen changed tests claim reset behavior, supplied-prop effects, scrolling, or absence of an asynchronous request, read [scenario reachability](references\u002Fscenario-reachability.md).\n\nWhen a reusable package's published peer contract or packaging transform changes, read [published peer contracts](references\u002Fpublished-peer-contract.md).\nSee [references\u002Fcode-quality.md](references\u002Fcode-quality.md), [references\u002Fperformance.md](references\u002Fperformance.md), [references\u002Fbusiness-logic.md](references\u002Fbusiness-logic.md) for the living checklist split by category -- treat it as the canonical set of rules to follow.\n\nFlag each rule violation with urgency metadata so future reviewers can prioritize fixes.\n\n## Review Process\n1. Open the relevant component\u002Fmodule. Gather lines that relate to class names, React Flow hooks, prop memoization, and styling.\n2. For each rule in the review point, note where the code deviates and capture a representative snippet.\n3. Compose the review section per the template below. Group violations first by **Urgent** flag, then by category order (Code Quality, Performance, Business Logic).\n\n## Required output\nWhen invoked, the response must exactly follow one of the two templates:\n\n### Template A (any findings)\n```\n# Code review\nFound \u003CN> urgent issues need to be fixed:\n\n## 1 \u003Cbrief description of bug>\nFilePath: \u003Cpath> line \u003Cline>\n\u003Crelevant code snippet or pointer>\n\n\n### Suggested fix\n\u003Cbrief description of suggested fix>\n\n---\n... (repeat for each urgent issue) ...\n\nFound \u003CM> suggestions for improvement:\n\n## 1 \u003Cbrief description of suggestion>\nFilePath: \u003Cpath> line \u003Cline>\n\u003Crelevant code snippet or pointer>\n\n\n### Suggested fix\n\u003Cbrief description of suggested fix>\n\n---\n\n... (repeat for each suggestion) ...\n```\n\nIf there are no urgent issues, omit that section. If there are no suggestions, omit that section.\n\nIf the issue number is more than 10, summarize as \"10+ urgent issues\" or \"10+ suggestions\" and just output the first 10 issues.\n\nDon't compress the blank lines between sections; keep them as-is for readability.\n\nIf you use Template A (i.e., there are issues to fix) and at least one issue requires code changes, append a brief follow-up question after the structured output asking whether the user wants you to apply the suggested fix(es). For example: \"Would you like me to use the Suggested fix section to address these issues?\"\n\n### Template B (no issues)\n```\n## Code review\nNo issues found.\n```\n",{"name":5,"description":7},"main","3934845b800ff514cb89eb81d43f3dc4cbf51ff2","packages\u002Freact-frontend\u002Fskills\u002Ffrontend-code-review","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI","https:\u002F\u002Fgithub.com\u002Fsarthchawla","there ain't no problem i can't solve","2026-10-23 01:26:57",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add sarthchawla\u002FSetupMyAI --skill frontend-code-review",{"tool":70,"command":71},"bunx","bunx skills add sarthchawla\u002FSetupMyAI --skill frontend-code-review",{"tool":73,"command":74},"pnpm","pnpm dlx skills add sarthchawla\u002FSetupMyAI --skill frontend-code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Freact-frontend\u002Fskills\u002Ffrontend-code-review\u002FSKILL.md",true,[78,84,88,92,96],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fbusiness-logic.md","REFERENCE","参考文档",562,"https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Freact-frontend\u002Fskills\u002Ffrontend-code-review\u002Freferences\u002Fbusiness-logic.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fcode-quality.md",1431,"https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Freact-frontend\u002Fskills\u002Ffrontend-code-review\u002Freferences\u002Fcode-quality.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fperformance.md",927,"https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Freact-frontend\u002Fskills\u002Ffrontend-code-review\u002Freferences\u002Fperformance.md",{"path":93,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fpublished-peer-contract.md",2068,"https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Freact-frontend\u002Fskills\u002Ffrontend-code-review\u002Freferences\u002Fpublished-peer-contract.md",{"path":97,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fscenario-reachability.md",2795,"https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Freact-frontend\u002Fskills\u002Ffrontend-code-review\u002Freferences\u002Fscenario-reachability.md",[101,112,126,135,145,165],{"skillNo":102,"name":103,"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":104,"categories":105,"keywords":109,"publishedAt":52},"01M6P8953HNC422WFQSPP2FMQE","sample-skill","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmock-repo\u002F.claude\u002Fskills\u002Fsample-skill\u002FSKILL.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[110,111],"sample","sample skill",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":52},"01M6P8924ZSDAZ88Y5Q9P3KAQV","synthetic-review-candidate","Candidate for smoke testing an evaluation runner only.","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fscripts\u002Fskill-eval\u002Ffixtures\u002Fcandidate\u002FSKILL.md",[],[119,120,121,33,43,122,123,124,125,38],"synthetic review candidate","candidate","synthetic","testing","Evaluation","smoke","runner",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":52},"01M6P88FEGGNH8EZY0PDHD9KQA","synthetic-review-baseline","Baseline for smoke testing an evaluation runner only.","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fscripts\u002Fskill-eval\u002Ffixtures\u002Fbaseline\u002FSKILL.md",[],[133,121,134,33,124,125,38,43,122,123],"synthetic review baseline","baseline",{"skillNo":136,"name":33,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":52},"01M6P87ZXVEHRM860960DB5FEQ","Run the existing user-invoked review bundle and independently adjudicate its findings.","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal\u002Fskills\u002Freview\u002FSKILL.md",[],[33,141,142,143,144],"run","user","bundle","Existing",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":52},"01M6P87FC73MZTRB6ZBP4GR1VQ","review-adjudication","Verify generated or human review findings before fixing, defending, replying, resolving, or reusing them as learned guidance. Use within a review, review-comment fix, monitor, or readiness workflow.","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal\u002Fskills\u002Freview-adjudication\u002FSKILL.md",[],[152,33,153,154,155,156,157,158,159,160,161,162,45,163,164],"review adjudication","workflow","generated","human review","guidance","human","as","readiness","learned","review findings","fix","verify","monitor",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":52},"01M6P871Q44KQES293T60JQETA","monitor-mr","Monitor review findings and CI using the shared adjudication procedure.","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal\u002Fskills\u002Fmonitor-mr\u002FSKILL.md",[],[164,172,173,161,174,175,33],"mr","monitor mr","shared","ci"]