[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75G50WJR10SWMPNWFF7XC20":3,"skill-same:01M75G50WJR10SWMPNWFF7XC20":51},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75G50WJR10SWMPNWFF7XC20","multi-reviewer-patterns",null,"Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.","RudyCity\u002Fsuperagent","RudyCity","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82188919?v=4","01M75FP5X8AW8ACBH0SH34WS7M","01M75FP5YAHJK8M1Q52BWXB82K",70,"MIT","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmulti-reviewer-patterns\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: multi-reviewer-patterns\ndescription: Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.\nversion: 1.0.2\n---\n\n# Multi-Reviewer Patterns\n\nPatterns for coordinating parallel code reviews across multiple quality dimensions, deduplicating findings, calibrating severity, and producing consolidated reports.\n\n## When to Use This Skill\n\n- Organizing a multi-dimensional code review\n- Deciding which review dimensions to assign\n- Deduplicating findings from multiple reviewers\n- Calibrating severity ratings consistently\n- Producing a consolidated review report\n\n## Review Dimension Allocation\n\n### Available Dimensions\n\n| Dimension         | Focus                                   | When to Include                             |\n| ----------------- | --------------------------------------- | ------------------------------------------- |\n| **Security**      | Vulnerabilities, auth, input validation | Always for code handling user input or auth |\n| **Performance**   | Query efficiency, memory, caching       | When changing data access or hot paths      |\n| **Architecture**  | SOLID, coupling, patterns               | For structural changes or new modules       |\n| **Testing**       | Coverage, quality, edge cases           | When adding new functionality               |\n| **Accessibility** | WCAG, ARIA, keyboard nav                | For UI\u002Ffrontend changes                     |\n\n### Recommended Combinations\n\n| Scenario               | Dimensions                                   |\n| ---------------------- | -------------------------------------------- |\n| API endpoint changes   | Security, Performance, Architecture          |\n| Frontend component     | Architecture, Testing, Accessibility         |\n| Database migration     | Performance, Architecture                    |\n| Authentication changes | Security, Testing                            |\n| Full feature review    | Security, Performance, Architecture, Testing |\n\n## Finding Deduplication\n\nWhen multiple reviewers report issues at the same location:\n\n### Merge Rules\n\n1. **Same file:line, same issue** — Merge into one finding, credit all reviewers\n2. **Same file:line, different issues** — Keep as separate findings\n3. **Same issue, different locations** — Keep separate but cross-reference\n4. **Conflicting severity** — Use the higher severity rating\n5. **Conflicting recommendations** — Include both with reviewer attribution\n\n### Deduplication Process\n\n```\nFor each finding in all reviewer reports:\n  1. Check if another finding references the same file:line\n  2. If yes, check if they describe the same issue\n  3. If same issue: merge, keeping the more detailed description\n  4. If different issue: keep both, tag as \"co-located\"\n  5. Use highest severity among merged findings\n```\n\n## Severity Calibration\n\n### Severity Criteria\n\n| Severity     | Impact                                        | Likelihood             | Examples                                     |\n| ------------ | --------------------------------------------- | ---------------------- | -------------------------------------------- |\n| **Critical** | Data loss, security breach, complete failure  | Certain or very likely | SQL injection, auth bypass, data corruption  |\n| **High**     | Significant functionality impact, degradation | Likely                 | Memory leak, missing validation, broken flow |\n| **Medium**   | Partial impact, workaround exists             | Possible               | N+1 query, missing edge case, unclear error  |\n| **Low**      | Minimal impact, cosmetic                      | Unlikely               | Style issue, minor optimization, naming      |\n\n### Calibration Rules\n\n- Security vulnerabilities exploitable by external users: always Critical or High\n- Performance issues in hot paths: at least Medium\n- Missing tests for critical paths: at least Medium\n- Accessibility violations for core functionality: at least Medium\n- Code style issues with no functional impact: Low\n\n## Consolidated Report Template\n\n```markdown\n## Code Review Report\n\n**Target**: {files\u002FPR\u002Fdirectory}\n**Reviewers**: {dimension-1}, {dimension-2}, {dimension-3}\n**Date**: {date}\n**Files Reviewed**: {count}\n\n### Critical Findings ({count})\n\n#### [CR-001] {Title}\n\n**Location**: `{file}:{line}`\n**Dimension**: {Security\u002FPerformance\u002Fetc.}\n**Description**: {what was found}\n**Impact**: {what could happen}\n**Fix**: {recommended remediation}\n\n### High Findings ({count})\n\n...\n\n### Medium Findings ({count})\n\n...\n\n### Low Findings ({count})\n\n...\n\n### Summary\n\n| Dimension    | Critical | High  | Medium | Low   | Total  |\n| ------------ | -------- | ----- | ------ | ----- | ------ |\n| Security     | 1        | 2     | 3      | 0     | 6      |\n| Performance  | 0        | 1     | 4      | 2     | 7      |\n| Architecture | 0        | 0     | 2      | 3     | 5      |\n| **Total**    | **1**    | **3** | **9**  | **5** | **18** |\n\n### Recommendation\n\n{Overall assessment and prioritized action items}\n```\n","# Multi-Reviewer Patterns\n\nPatterns for coordinating parallel code reviews across multiple quality dimensions, deduplicating findings, calibrating severity, and producing consolidated reports.\n\n## When to Use This Skill\n\n- Organizing a multi-dimensional code review\n- Deciding which review dimensions to assign\n- Deduplicating findings from multiple reviewers\n- Calibrating severity ratings consistently\n- Producing a consolidated review report\n\n## Review Dimension Allocation\n\n### Available Dimensions\n\n| Dimension         | Focus                                   | When to Include                             |\n| ----------------- | --------------------------------------- | ------------------------------------------- |\n| **Security**      | Vulnerabilities, auth, input validation | Always for code handling user input or auth |\n| **Performance**   | Query efficiency, memory, caching       | When changing data access or hot paths      |\n| **Architecture**  | SOLID, coupling, patterns               | For structural changes or new modules       |\n| **Testing**       | Coverage, quality, edge cases           | When adding new functionality               |\n| **Accessibility** | WCAG, ARIA, keyboard nav                | For UI\u002Ffrontend changes                     |\n\n### Recommended Combinations\n\n| Scenario               | Dimensions                                   |\n| ---------------------- | -------------------------------------------- |\n| API endpoint changes   | Security, Performance, Architecture          |\n| Frontend component     | Architecture, Testing, Accessibility         |\n| Database migration     | Performance, Architecture                    |\n| Authentication changes | Security, Testing                            |\n| Full feature review    | Security, Performance, Architecture, Testing |\n\n## Finding Deduplication\n\nWhen multiple reviewers report issues at the same location:\n\n### Merge Rules\n\n1. **Same file:line, same issue** — Merge into one finding, credit all reviewers\n2. **Same file:line, different issues** — Keep as separate findings\n3. **Same issue, different locations** — Keep separate but cross-reference\n4. **Conflicting severity** — Use the higher severity rating\n5. **Conflicting recommendations** — Include both with reviewer attribution\n\n### Deduplication Process\n\n```\nFor each finding in all reviewer reports:\n  1. Check if another finding references the same file:line\n  2. If yes, check if they describe the same issue\n  3. If same issue: merge, keeping the more detailed description\n  4. If different issue: keep both, tag as \"co-located\"\n  5. Use highest severity among merged findings\n```\n\n## Severity Calibration\n\n### Severity Criteria\n\n| Severity     | Impact                                        | Likelihood             | Examples                                     |\n| ------------ | --------------------------------------------- | ---------------------- | -------------------------------------------- |\n| **Critical** | Data loss, security breach, complete failure  | Certain or very likely | SQL injection, auth bypass, data corruption  |\n| **High**     | Significant functionality impact, degradation | Likely                 | Memory leak, missing validation, broken flow |\n| **Medium**   | Partial impact, workaround exists             | Possible               | N+1 query, missing edge case, unclear error  |\n| **Low**      | Minimal impact, cosmetic                      | Unlikely               | Style issue, minor optimization, naming      |\n\n### Calibration Rules\n\n- Security vulnerabilities exploitable by external users: always Critical or High\n- Performance issues in hot paths: at least Medium\n- Missing tests for critical paths: at least Medium\n- Accessibility violations for core functionality: at least Medium\n- Code style issues with no functional impact: Low\n\n## Consolidated Report Template\n\n```markdown\n## Code Review Report\n\n**Target**: {files\u002FPR\u002Fdirectory}\n**Reviewers**: {dimension-1}, {dimension-2}, {dimension-3}\n**Date**: {date}\n**Files Reviewed**: {count}\n\n### Critical Findings ({count})\n\n#### [CR-001] {Title}\n\n**Location**: `{file}:{line}`\n**Dimension**: {Security\u002FPerformance\u002Fetc.}\n**Description**: {what was found}\n**Impact**: {what could happen}\n**Fix**: {recommended remediation}\n\n### High Findings ({count})\n\n...\n\n### Medium Findings ({count})\n\n...\n\n### Low Findings ({count})\n\n...\n\n### Summary\n\n| Dimension    | Critical | High  | Medium | Low   | Total  |\n| ------------ | -------- | ----- | ------ | ----- | ------ |\n| Security     | 1        | 2     | 3      | 0     | 6      |\n| Performance  | 0        | 1     | 4      | 2     | 7      |\n| Architecture | 0        | 0     | 2      | 3     | 5      |\n| **Total**    | **1**    | **3** | **9**  | **5** | **18** |\n\n### Recommendation\n\n{Overall assessment and prioritized action items}\n```\n",{"name":5,"version":23,"description":7},"1.0.2","main","62c7af5ced2c21355d148c243edb6d5921cca1a6",".agents\u002Fskills\u002Fmulti-reviewer-patterns",8,"https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent","https:\u002F\u002Fgithub.com\u002FRudyCity","2026-11-14 22:58:49",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add RudyCity\u002Fsuperagent --skill multi-reviewer-patterns",{"tool":37,"command":38},"bunx","bunx skills add RudyCity\u002Fsuperagent --skill multi-reviewer-patterns",{"tool":40,"command":41},"pnpm","pnpm dlx skills add RudyCity\u002Fsuperagent --skill multi-reviewer-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmulti-reviewer-patterns\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Freview-dimensions.md","REFERENCE","参考文档",4107,"https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmulti-reviewer-patterns\u002Freferences\u002Freview-dimensions.md",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M75GP28CM6QCSXSHKFF3NNKS","telegram_bot","Use Telegram Bot when the user asks for Telegram Bot or this provider's API.","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002Fmuse-bridge-kit\u002Fskills\u002Ftelegram-bot\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M75GNZGZYM7NWDV6MBP3HS14","superagent-bridge","Operate the Muse\u003C->superagent Telegram bridge: poll the private group for task_request\u002Ftask_result envelopes, validate senders, and reply with task_batch\u002Ftask_done as Muse (the remote brain).","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002Fmuse-bridge-kit\u002Fskills\u002Fsuperagent-bridge\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75GNHN19HJWZ7NAPM5E5JCV","Writing Skills","TDD for process documentation - test with subagents before writing, iterate until bulletproof","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75GNCQEKVRA4FH161NZPZNB","writing-shape","Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75GNAF9NAYCSTBDZDGMK0DZ","Writing Plans","Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M75GN72EV0V5NQAW9CSPFRFH","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[]]