[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SN02MNQA4S3JZ4FMSRFDE":3,"skill-same:01M79SN02MNQA4S3JZ4FMSRFDE":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":13,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M79SN02MNQA4S3JZ4FMSRFDE","code-reviewer",null,"Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality. Complements specialized skills (security-reviewer, test-master) by providing broad-scope review across correctness, performance, maintainability, and test coverage in a single pass.","Snuc1925\u002FSWE-AI-Agent","Snuc1925","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87866086?v=4","01M79SEFKVJ24BEZS59RCHPNSX","01M79SEFMJFYTNK7S8WF299CWN",0,"MIT","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fcode-quality\u002Fcode-reviewer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: code-reviewer\ndescription: Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality. Complements specialized skills (security-reviewer, test-master) by providing broad-scope review across correctness, performance, maintainability, and test coverage in a single pass.\nlicense: MIT\nallowed-tools: Read, Grep, Glob\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: quality\n  triggers: code review, PR review, pull request, review code, code quality\n  role: specialist\n  scope: review\n  output-format: report\n  related-skills: security-reviewer, test-master, architecture-designer\n---\n\n# Code Reviewer\n\nSenior engineer conducting thorough, constructive code reviews that improve quality and share knowledge.\n\n## When to Use This Skill\n\n- Reviewing pull requests\n- Conducting code quality audits\n- Identifying refactoring opportunities\n- Checking for security vulnerabilities\n- Validating architectural decisions\n\n## Core Workflow\n\n1. **Context** — Read PR description, understand the problem being solved. **Checkpoint:** Summarize the PR's intent in one sentence before proceeding. If you cannot, ask the author to clarify.\n2. **Structure** — Review architecture and design decisions. Ask: Does this follow existing patterns in the codebase? Are new abstractions justified?\n3. **Details** — Check code quality, security, and performance. Apply the checks in the Reference Guide below. Ask: Are there N+1 queries, hardcoded secrets, or injection risks?\n4. **Tests** — Validate test coverage and quality. Ask: Are edge cases covered? Do tests assert behavior, not implementation?\n5. **Feedback** — Produce a categorized report using the Output Template. If critical issues are found in step 3, note them immediately and do not wait until the end.\n\n> **Disagreement handling:** If the author has left comments explaining a non-obvious choice, acknowledge their reasoning before suggesting an alternative. Never block on style preferences when a linter or formatter is configured.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n\u003C!-- Spec Compliance and Receiving Feedback rows adapted from obra\u002Fsuperpowers by Jesse Vincent (@obra), MIT License -->\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Review Checklist | `references\u002Freview-checklist.md` | Starting a review, categories |\n| Common Issues | `references\u002Fcommon-issues.md` | N+1 queries, magic numbers, patterns |\n| Feedback Examples | `references\u002Ffeedback-examples.md` | Writing good feedback |\n| Report Template | `references\u002Freport-template.md` | Writing final review report |\n| Spec Compliance | `references\u002Fspec-compliance-review.md` | Reviewing implementations, PR review, spec verification |\n| Receiving Feedback | `references\u002Freceiving-feedback.md` | Responding to review comments, handling feedback |\n\n## Review Patterns (Quick Reference)\n\n### N+1 Query — Bad vs Good\n```python\n# BAD: query inside loop\nfor user in users:\n    orders = Order.objects.filter(user=user)  # N+1\n\n# GOOD: prefetch in bulk\nusers = User.objects.prefetch_related('orders').all()\n```\n\n### Magic Number — Bad vs Good\n```python\n# BAD\nif status == 3:\n    ...\n\n# GOOD\nORDER_STATUS_SHIPPED = 3\nif status == ORDER_STATUS_SHIPPED:\n    ...\n```\n\n### Security: SQL Injection — Bad vs Good\n```python\n# BAD: string interpolation in query\ncursor.execute(f\"SELECT * FROM users WHERE id = {user_id}\")\n\n# GOOD: parameterized query\ncursor.execute(\"SELECT * FROM users WHERE id = %s\", [user_id])\n```\n\n## Constraints\n\n### MUST DO\n- Summarize PR intent before reviewing (see Workflow step 1)\n- Provide specific, actionable feedback\n- Include code examples in suggestions\n- Praise good patterns\n- Prioritize feedback (critical → minor)\n- Review tests as thoroughly as code\n- Check for security issues (OWASP Top 10 as baseline)\n\n### MUST NOT DO\n- Be condescending or rude\n- Nitpick style when linters exist\n- Block on personal preferences\n- Demand perfection\n- Review without understanding the why\n- Skip praising good work\n\n## Output Template\n\nCode review report must include:\n1. **Summary** — One-sentence intent recap + overall assessment\n2. **Critical issues** — Must fix before merge (bugs, security, data loss)\n3. **Major issues** — Should fix (performance, design, maintainability)\n4. **Minor issues** — Nice to have (naming, readability)\n5. **Positive feedback** — Specific patterns done well\n6. **Questions for author** — Clarifications needed\n7. **Verdict** — Approve \u002F Request Changes \u002F Comment\n\n## Knowledge Reference\n\nSOLID, DRY, KISS, YAGNI, design patterns, OWASP Top 10, language idioms, testing patterns\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fquality\u002Fcode-reviewer\u002F)\n","# Code Reviewer\n\nSenior engineer conducting thorough, constructive code reviews that improve quality and share knowledge.\n\n## When to Use This Skill\n\n- Reviewing pull requests\n- Conducting code quality audits\n- Identifying refactoring opportunities\n- Checking for security vulnerabilities\n- Validating architectural decisions\n\n## Core Workflow\n\n1. **Context** — Read PR description, understand the problem being solved. **Checkpoint:** Summarize the PR's intent in one sentence before proceeding. If you cannot, ask the author to clarify.\n2. **Structure** — Review architecture and design decisions. Ask: Does this follow existing patterns in the codebase? Are new abstractions justified?\n3. **Details** — Check code quality, security, and performance. Apply the checks in the Reference Guide below. Ask: Are there N+1 queries, hardcoded secrets, or injection risks?\n4. **Tests** — Validate test coverage and quality. Ask: Are edge cases covered? Do tests assert behavior, not implementation?\n5. **Feedback** — Produce a categorized report using the Output Template. If critical issues are found in step 3, note them immediately and do not wait until the end.\n\n> **Disagreement handling:** If the author has left comments explaining a non-obvious choice, acknowledge their reasoning before suggesting an alternative. Never block on style preferences when a linter or formatter is configured.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n\u003C!-- Spec Compliance and Receiving Feedback rows adapted from obra\u002Fsuperpowers by Jesse Vincent (@obra), MIT License -->\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Review Checklist | `references\u002Freview-checklist.md` | Starting a review, categories |\n| Common Issues | `references\u002Fcommon-issues.md` | N+1 queries, magic numbers, patterns |\n| Feedback Examples | `references\u002Ffeedback-examples.md` | Writing good feedback |\n| Report Template | `references\u002Freport-template.md` | Writing final review report |\n| Spec Compliance | `references\u002Fspec-compliance-review.md` | Reviewing implementations, PR review, spec verification |\n| Receiving Feedback | `references\u002Freceiving-feedback.md` | Responding to review comments, handling feedback |\n\n## Review Patterns (Quick Reference)\n\n### N+1 Query — Bad vs Good\n```python\n# BAD: query inside loop\nfor user in users:\n    orders = Order.objects.filter(user=user)  # N+1\n\n# GOOD: prefetch in bulk\nusers = User.objects.prefetch_related('orders').all()\n```\n\n### Magic Number — Bad vs Good\n```python\n# BAD\nif status == 3:\n    ...\n\n# GOOD\nORDER_STATUS_SHIPPED = 3\nif status == ORDER_STATUS_SHIPPED:\n    ...\n```\n\n### Security: SQL Injection — Bad vs Good\n```python\n# BAD: string interpolation in query\ncursor.execute(f\"SELECT * FROM users WHERE id = {user_id}\")\n\n# GOOD: parameterized query\ncursor.execute(\"SELECT * FROM users WHERE id = %s\", [user_id])\n```\n\n## Constraints\n\n### MUST DO\n- Summarize PR intent before reviewing (see Workflow step 1)\n- Provide specific, actionable feedback\n- Include code examples in suggestions\n- Praise good patterns\n- Prioritize feedback (critical → minor)\n- Review tests as thoroughly as code\n- Check for security issues (OWASP Top 10 as baseline)\n\n### MUST NOT DO\n- Be condescending or rude\n- Nitpick style when linters exist\n- Block on personal preferences\n- Demand perfection\n- Review without understanding the why\n- Skip praising good work\n\n## Output Template\n\nCode review report must include:\n1. **Summary** — One-sentence intent recap + overall assessment\n2. **Critical issues** — Must fix before merge (bugs, security, data loss)\n3. **Major issues** — Should fix (performance, design, maintainability)\n4. **Minor issues** — Nice to have (naming, readability)\n5. **Positive feedback** — Specific patterns done well\n6. **Questions for author** — Clarifications needed\n7. **Verdict** — Approve \u002F Request Changes \u002F Comment\n\n## Knowledge Reference\n\nSOLID, DRY, KISS, YAGNI, design patterns, OWASP Top 10, language idioms, testing patterns\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fquality\u002Fcode-reviewer\u002F)\n",{"name":5,"license":14,"metadata":23,"description":7,"allowed-tools":32},{"role":24,"scope":25,"author":26,"domain":27,"version":28,"triggers":29,"output-format":30,"related-skills":31},"specialist","review","https:\u002F\u002Fgithub.com\u002FJeffallan","quality","1.1.0","code review, PR review, pull request, review code, code quality","report","security-reviewer, test-master, architecture-designer","Read, Grep, Glob","main","459326d435e3b6ae17300b946bd4b7458ecd2bae","skill-library\u002Fcode-quality\u002Fcode-reviewer","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent","https:\u002F\u002Fgithub.com\u002FSnuc1925","2026-07-29 09:46:52",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add Snuc1925\u002FSWE-AI-Agent --skill code-reviewer",{"tool":45,"command":46},"bunx","bunx skills add Snuc1925\u002FSWE-AI-Agent --skill code-reviewer",{"tool":48,"command":49},"pnpm","pnpm dlx skills add Snuc1925\u002FSWE-AI-Agent --skill code-reviewer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fcode-quality\u002Fcode-reviewer\u002FSKILL.md",true,[],[54,63,71,79,86,94],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":58,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M79T5E59T5HMWZVTFJA9QXN1","linear","Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fworkflow-planning\u002Flinear\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fworkflow-planning\u002Flinear\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":58,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M79T535TSDZ09RXZ2YPEE3TN","define-goal","Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fworkflow-planning\u002Fdefine-goal\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Fworkflow-planning\u002Fdefine-goal\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":58,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M79T4TE9NAVN5REZVETVXBCN","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M79T4HSEDWY2NXVRDZ3RX7J4","test-master","Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Ftest-master\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":58,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M79T43SW5P3Y37F6Y82T76EM","playwright","Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fplaywright\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fplaywright\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":58,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M79T3ZYPH547MMC5FFBY1APS","playwright-interactive","Persistent browser and Electron interaction through `js_repl` for fast iterative UI debugging.","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fplaywright-interactive\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSnuc1925\u002FSWE-AI-Agent\u002Fblob\u002Fmain\u002Fskill-library\u002Ftesting\u002Fplaywright-interactive\u002FSKILL.md",[],[]]