[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EHPRFZF836PBCD3SCHXCF9":3,"skill-same:01M7EHPRFZF836PBCD3SCHXCF9":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7EHPRFZF836PBCD3SCHXCF9","differential-review",null,"Security-focused code review for PRs, commits, and diffs.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fdifferential-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: differential-review\ndescription: \"Security-focused code review for PRs, commits, and diffs.\"\nrisk: critical\nsource: community\ndate_added: \"2026-09-04\"\n---\n\n# Differential Security Review\n\nSecurity-focused code review for PRs, commits, and diffs.\n\n## When to Use\n- You need a security-focused review of a PR, commit range, or diff rather than a general code review.\n- The changes touch auth, crypto, external calls, value transfer, permissions, or other high-risk logic.\n- You need findings backed by code evidence, attack scenarios, and an explicit report artifact.\n\n## Core Principles\n\n1. **Risk-First**: Focus on auth, crypto, value transfer, external calls\n2. **Evidence-Based**: Every finding backed by git history, line numbers, attack scenarios\n3. **Adaptive**: Scale to codebase size (SMALL\u002FMEDIUM\u002FLARGE)\n4. **Honest**: Explicitly state coverage limits and confidence level\n5. **Output-Driven**: Always generate comprehensive markdown report file\n\n---\n\n## Rationalizations (Do Not Skip)\n\n| Rationalization | Why It's Wrong | Required Action |\n|-----------------|----------------|-----------------|\n| \"Small PR, quick review\" | Heartbleed was 2 lines | Classify by RISK, not size |\n| \"I know this codebase\" | Familiarity breeds blind spots | Build explicit baseline context |\n| \"Git history takes too long\" | History reveals regressions | Never skip Phase 1 |\n| \"Blast radius is obvious\" | You'll miss transitive callers | Calculate quantitatively |\n| \"No tests = not my problem\" | Missing tests = elevated risk rating | Flag in report, elevate severity |\n| \"Just a refactor, no security impact\" | Refactors break invariants | Analyze as HIGH until proven LOW |\n| \"I'll explain verbally\" | No artifact = findings lost | Always write report |\n\n---\n\n## Quick Reference\n\n### Codebase Size Strategy\n\n| Codebase Size | Strategy | Approach |\n|---------------|----------|----------|\n| SMALL (\u003C20 files) | DEEP | Read all deps, full git blame |\n| MEDIUM (20-200) | FOCUSED | 1-hop deps, priority files |\n| LARGE (200+) | SURGICAL | Critical paths only |\n\n### Risk Level Triggers\n\n| Risk Level | Triggers |\n|------------|----------|\n| HIGH | Auth, crypto, external calls, value transfer, validation removal |\n| MEDIUM | Business logic, state changes, new public APIs |\n| LOW | Comments, tests, UI, logging |\n\n---\n\n## Workflow Overview\n\n```\nPre-Analysis → Phase 0: Triage → Phase 1: Code Analysis → Phase 2: Test Coverage\n    ↓              ↓                    ↓                        ↓\nPhase 3: Blast Radius → Phase 4: Deep Context → Phase 5: Adversarial → Phase 6: Report\n```\n\n---\n\n## Decision Tree\n\n**Starting a review?**\n\n```\n├─ Need detailed phase-by-phase methodology?\n│  └─ Read: methodology.md\n│     (Pre-Analysis + Phases 0-4: triage, code analysis, test coverage, blast radius)\n│\n├─ Analyzing HIGH RISK change?\n│  └─ Read: adversarial.md\n│     (Phase 5: Attacker modeling, exploit scenarios, exploitability rating)\n│\n├─ Writing the final report?\n│  └─ Read: reporting.md\n│     (Phase 6: Report structure, templates, formatting guidelines)\n│\n├─ Looking for specific vulnerability patterns?\n│  └─ Read: patterns.md\n│     (Regressions, reentrancy, access control, overflow, etc.)\n│\n└─ Quick triage only?\n   └─ Use Quick Reference above, skip detailed docs\n```\n\n---\n\n## Quality Checklist\n\nBefore delivering:\n\n- [ ] All changed files analyzed\n- [ ] Git blame on removed security code\n- [ ] Blast radius calculated for HIGH risk\n- [ ] Attack scenarios are concrete (not generic)\n- [ ] Findings reference specific line numbers + commits\n- [ ] Report file generated\n- [ ] User notified with summary\n\n---\n\n## Integration\n\n**audit-context-building skill:**\n- Pre-Analysis: Build baseline context\n- Phase 4: Deep context on HIGH RISK changes\n\n**issue-writer skill:**\n- Transform findings into formal audit reports\n- Command: `issue-writer --input DIFFERENTIAL_REVIEW_REPORT.md --format audit-report`\n\n---\n\n## Example Usage\n\n### Quick Triage (Small PR)\n```\nInput: 5 file PR, 2 HIGH RISK files\nStrategy: Use Quick Reference\n1. Classify risk level per file (2 HIGH, 3 LOW)\n2. Focus on 2 HIGH files only\n3. Git blame removed code\n4. Generate minimal report\nTime: ~30 minutes\n```\n\n### Standard Review (Medium Codebase)\n```\nInput: 80 files, 12 HIGH RISK changes\nStrategy: FOCUSED (see methodology.md)\n1. Full workflow on HIGH RISK files\n2. Surface scan on MEDIUM\n3. Skip LOW risk files\n4. Complete report with all sections\nTime: ~3-4 hours\n```\n\n### Deep Audit (Large, Critical Change)\n```\nInput: 450 files, auth system rewrite\nStrategy: SURGICAL + audit-context-building\n1. Baseline context with audit-context-building\n2. Deep analysis on auth changes only\n3. Blast radius analysis\n4. Adversarial modeling\n5. Comprehensive report\nTime: ~6-8 hours\n```\n\n---\n\n## When NOT to Use This Skill\n\n- **Greenfield code** (no baseline to compare)\n- **Documentation-only changes** (no security impact)\n- **Formatting\u002Flinting** (cosmetic changes)\n- **User explicitly requests quick summary only** (they accept risk)\n\nFor these cases, use standard code review instead.\n\n---\n\n## Red Flags (Stop and Investigate)\n\n**Immediate escalation triggers:**\n- Removed code from \"security\", \"CVE\", or \"fix\" commits\n- Access control modifiers removed (onlyOwner, internal → external)\n- Validation removed without replacement\n- External calls added without checks\n- High blast radius (50+ callers) + HIGH risk change\n\nThese patterns require adversarial analysis even in quick triage.\n\n---\n\n## Tips for Best Results\n\n**Do:**\n- Start with git blame for removed code\n- Calculate blast radius early to prioritize\n- Generate concrete attack scenarios\n- Reference specific line numbers and commits\n- Be honest about coverage limitations\n- Always generate the output file\n\n**Don't:**\n- Skip git history analysis\n- Make generic findings without evidence\n- Claim full analysis when time-limited\n- Forget to check test coverage\n- Miss high blast radius changes\n- Output report only to chat (file required)\n\n---\n\n## Supporting Documentation\n\n- **methodology.md** - Detailed phase-by-phase workflow (Phases 0-4)\n- **adversarial.md** - Attacker modeling and exploit scenarios (Phase 5)\n- **reporting.md** - Report structure and formatting (Phase 6)\n- **patterns.md** - Common vulnerability patterns reference\n\n---\n\n**For first-time users:** Start with methodology.md to understand the complete workflow.\n\n**For experienced users:** Use this page's Quick Reference and Decision Tree to navigate directly to needed content.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Differential Security Review\n\nSecurity-focused code review for PRs, commits, and diffs.\n\n## When to Use\n- You need a security-focused review of a PR, commit range, or diff rather than a general code review.\n- The changes touch auth, crypto, external calls, value transfer, permissions, or other high-risk logic.\n- You need findings backed by code evidence, attack scenarios, and an explicit report artifact.\n\n## Core Principles\n\n1. **Risk-First**: Focus on auth, crypto, value transfer, external calls\n2. **Evidence-Based**: Every finding backed by git history, line numbers, attack scenarios\n3. **Adaptive**: Scale to codebase size (SMALL\u002FMEDIUM\u002FLARGE)\n4. **Honest**: Explicitly state coverage limits and confidence level\n5. **Output-Driven**: Always generate comprehensive markdown report file\n\n---\n\n## Rationalizations (Do Not Skip)\n\n| Rationalization | Why It's Wrong | Required Action |\n|-----------------|----------------|-----------------|\n| \"Small PR, quick review\" | Heartbleed was 2 lines | Classify by RISK, not size |\n| \"I know this codebase\" | Familiarity breeds blind spots | Build explicit baseline context |\n| \"Git history takes too long\" | History reveals regressions | Never skip Phase 1 |\n| \"Blast radius is obvious\" | You'll miss transitive callers | Calculate quantitatively |\n| \"No tests = not my problem\" | Missing tests = elevated risk rating | Flag in report, elevate severity |\n| \"Just a refactor, no security impact\" | Refactors break invariants | Analyze as HIGH until proven LOW |\n| \"I'll explain verbally\" | No artifact = findings lost | Always write report |\n\n---\n\n## Quick Reference\n\n### Codebase Size Strategy\n\n| Codebase Size | Strategy | Approach |\n|---------------|----------|----------|\n| SMALL (\u003C20 files) | DEEP | Read all deps, full git blame |\n| MEDIUM (20-200) | FOCUSED | 1-hop deps, priority files |\n| LARGE (200+) | SURGICAL | Critical paths only |\n\n### Risk Level Triggers\n\n| Risk Level | Triggers |\n|------------|----------|\n| HIGH | Auth, crypto, external calls, value transfer, validation removal |\n| MEDIUM | Business logic, state changes, new public APIs |\n| LOW | Comments, tests, UI, logging |\n\n---\n\n## Workflow Overview\n\n```\nPre-Analysis → Phase 0: Triage → Phase 1: Code Analysis → Phase 2: Test Coverage\n    ↓              ↓                    ↓                        ↓\nPhase 3: Blast Radius → Phase 4: Deep Context → Phase 5: Adversarial → Phase 6: Report\n```\n\n---\n\n## Decision Tree\n\n**Starting a review?**\n\n```\n├─ Need detailed phase-by-phase methodology?\n│  └─ Read: methodology.md\n│     (Pre-Analysis + Phases 0-4: triage, code analysis, test coverage, blast radius)\n│\n├─ Analyzing HIGH RISK change?\n│  └─ Read: adversarial.md\n│     (Phase 5: Attacker modeling, exploit scenarios, exploitability rating)\n│\n├─ Writing the final report?\n│  └─ Read: reporting.md\n│     (Phase 6: Report structure, templates, formatting guidelines)\n│\n├─ Looking for specific vulnerability patterns?\n│  └─ Read: patterns.md\n│     (Regressions, reentrancy, access control, overflow, etc.)\n│\n└─ Quick triage only?\n   └─ Use Quick Reference above, skip detailed docs\n```\n\n---\n\n## Quality Checklist\n\nBefore delivering:\n\n- [ ] All changed files analyzed\n- [ ] Git blame on removed security code\n- [ ] Blast radius calculated for HIGH risk\n- [ ] Attack scenarios are concrete (not generic)\n- [ ] Findings reference specific line numbers + commits\n- [ ] Report file generated\n- [ ] User notified with summary\n\n---\n\n## Integration\n\n**audit-context-building skill:**\n- Pre-Analysis: Build baseline context\n- Phase 4: Deep context on HIGH RISK changes\n\n**issue-writer skill:**\n- Transform findings into formal audit reports\n- Command: `issue-writer --input DIFFERENTIAL_REVIEW_REPORT.md --format audit-report`\n\n---\n\n## Example Usage\n\n### Quick Triage (Small PR)\n```\nInput: 5 file PR, 2 HIGH RISK files\nStrategy: Use Quick Reference\n1. Classify risk level per file (2 HIGH, 3 LOW)\n2. Focus on 2 HIGH files only\n3. Git blame removed code\n4. Generate minimal report\nTime: ~30 minutes\n```\n\n### Standard Review (Medium Codebase)\n```\nInput: 80 files, 12 HIGH RISK changes\nStrategy: FOCUSED (see methodology.md)\n1. Full workflow on HIGH RISK files\n2. Surface scan on MEDIUM\n3. Skip LOW risk files\n4. Complete report with all sections\nTime: ~3-4 hours\n```\n\n### Deep Audit (Large, Critical Change)\n```\nInput: 450 files, auth system rewrite\nStrategy: SURGICAL + audit-context-building\n1. Baseline context with audit-context-building\n2. Deep analysis on auth changes only\n3. Blast radius analysis\n4. Adversarial modeling\n5. Comprehensive report\nTime: ~6-8 hours\n```\n\n---\n\n## When NOT to Use This Skill\n\n- **Greenfield code** (no baseline to compare)\n- **Documentation-only changes** (no security impact)\n- **Formatting\u002Flinting** (cosmetic changes)\n- **User explicitly requests quick summary only** (they accept risk)\n\nFor these cases, use standard code review instead.\n\n---\n\n## Red Flags (Stop and Investigate)\n\n**Immediate escalation triggers:**\n- Removed code from \"security\", \"CVE\", or \"fix\" commits\n- Access control modifiers removed (onlyOwner, internal → external)\n- Validation removed without replacement\n- External calls added without checks\n- High blast radius (50+ callers) + HIGH risk change\n\nThese patterns require adversarial analysis even in quick triage.\n\n---\n\n## Tips for Best Results\n\n**Do:**\n- Start with git blame for removed code\n- Calculate blast radius early to prioritize\n- Generate concrete attack scenarios\n- Reference specific line numbers and commits\n- Be honest about coverage limitations\n- Always generate the output file\n\n**Don't:**\n- Skip git history analysis\n- Make generic findings without evidence\n- Claim full analysis when time-limited\n- Forget to check test coverage\n- Miss high blast radius changes\n- Output report only to chat (file required)\n\n---\n\n## Supporting Documentation\n\n- **methodology.md** - Detailed phase-by-phase workflow (Phases 0-4)\n- **adversarial.md** - Attacker modeling and exploit scenarios (Phase 5)\n- **reporting.md** - Report structure and formatting (Phase 6)\n- **patterns.md** - Common vulnerability patterns reference\n\n---\n\n**For first-time users:** Start with methodology.md to understand the complete workflow.\n\n**For experienced users:** Use this page's Quick Reference and Decision Tree to navigate directly to needed content.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-09-04","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fdifferential-review",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill differential-review",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill differential-review",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill differential-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fdifferential-review\u002FSKILL.md",true,[],[50,58,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":57},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":59,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":57},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\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":57},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\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":57},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\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":57},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\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":57},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]