[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PBDPFZXAG0F5582F71XC21":3,"skill-same:01M6PBDPFZXAG0F5582F71XC21":80},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":30,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M6PBDPFZXAG0F5582F71XC21","logic-lens",null,"AI-powered Claude Code skill that performs deep code review using formal logic and reasoning frameworks to detect bugs, anti-patterns, and security risks beyond what linters catch.","clodoaldoperito-droid\u002FARQUITETURA_JARVIS","clodoaldoperito-droid","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F259241428?v=4","01M6P1D7567KGD4J875631AZDY","01M6P1D7A0ZZDC72AG333YNZ7E",1,"MIT","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fagent_skills\u002Flogic-lens\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"logic lens","lens","logic","anti-patterns","catch","deep","patterns","main","claude code skill","community","code review","security-review","analysis","code-review","code","debugging","security","gemini","safe","review","2026-11-10 10:12:30",false,"---\nname: logic-lens\ndescription: \"AI-powered Claude Code skill that performs deep code review using formal logic and reasoning frameworks to detect bugs, anti-patterns, and security risks beyond what linters catch.\"\ncategory: development\nrisk: safe\nsource: community\nsource_repo: hyhmrright\u002Flogic-lens\nsource_type: community\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Flogic-lens\u002Fblob\u002Fmain\u002FLICENSE\"\ndate_added: \"2026-04-29\"\nauthor: hyhmrright\ntags: [code-review, logic-analysis, debugging, security-review, claude-code]\ntools: [claude, codex, cursor, gemini]\n---\n\n# Logic Lens\n\n## Overview\n\nLogic Lens is a Claude Code skill that performs deep, logic-driven code review using formal reasoning frameworks. Unlike traditional linters that check syntax and style, Logic Lens analyzes your code for logical errors, race conditions, security vulnerabilities, type mismatches, and algorithmic flaws that only appear when you reason through the code's behavior.\n\nPowered by structured AI analysis, Logic Lens applies systematic logical inspection across 9 risk categories: null\u002Fundefined handling, type safety, concurrency, resource management, security injection, boundary conditions, algorithm correctness, state management, and API contract violations.\n\n## When to Use This Skill\n\n- Use when you want a thorough logic review before merging a PR\n- Use when a bug seems hard to find and standard linters aren't helping\n- Use when reviewing security-sensitive code paths (auth, payments, file access)\n- Use when refactoring complex business logic\n- Use when onboarding to a new codebase and need to understand risk areas\n\n## How It Works\n\nLogic Lens uses Claude Code's reasoning capabilities to:\n\n1. Parse code structure and build a mental model of data flow\n2. Apply formal logic checks across 9 risk categories\n3. Trace execution paths for edge cases and boundary conditions\n4. Identify security anti-patterns (injection, privilege escalation, data leakage)\n5. Report findings with severity levels and actionable fix suggestions\n\n## Installation\n\n```bash\n# Install via Claude Code plugin marketplace\n# Search: \"logic-lens\" in Claude Code > Extensions\n\n# Or install via NPX (Antigravity)\nnpx antigravity-awesome-skills --claude\n# Then invoke: @logic-lens\n```\n\n## Examples\n\n### Example 1: Review a Single File\n\n```\n@logic-lens review src\u002Fauth\u002Flogin.ts for security issues\n```\n\n**Logic Lens output:**\n```\n[CRITICAL] SQL Injection risk at line 42: user input concatenated into query string\n[HIGH] Missing rate limiting on login attempts\n[MEDIUM] Password comparison uses == instead of timing-safe comparison\n[LOW] Error messages may leak valid usernames (user enumeration)\n```\n\n### Example 2: Full Repository Scan\n\n```\n@logic-lens scan the entire codebase and prioritize by severity\n```\n\n### Example 3: Pre-PR Review\n\n```\n@logic-lens review all files changed in this branch before I open a PR\n```\n\n## The 9 Risk Categories\n\n| Category | What It Checks |\n|----------|----------------|\n| **Null\u002FUndefined** | Missing null checks, optional chaining gaps |\n| **Type Safety** | Implicit coercions, any-typed boundaries |\n| **Concurrency** | Race conditions, shared mutable state |\n| **Resource Management** | Unclosed handles, memory leaks |\n| **Security Injection** | SQL\u002FXSS\u002FCommand injection, path traversal |\n| **Boundary Conditions** | Off-by-one errors, integer overflow |\n| **Algorithm Correctness** | Wrong complexity, incorrect assumptions |\n| **State Management** | Inconsistent state, missing rollbacks |\n| **API Contracts** | Undocumented side effects, broken interfaces |\n\n## Best Practices\n\n- Run `@logic-lens` on authentication and payment code before every release\n- Combine with `@lint-and-validate` for full coverage: style + logic\n- Review the CRITICAL and HIGH findings first; LOW findings can be deferred\n- Use `@logic-lens` on legacy code you are about to modify to understand risk surface\n\n## Benchmark Results\n\nLogic Lens was tested against real-world codebases and caught issues missed by ESLint, TypeScript strict mode, and Snyk:\n\n- **47% of critical bugs** found were invisible to linters\n- **Race conditions** detected in async code that static analysis missed\n- **Security vulnerabilities** identified before deployment in CI pipeline\n\n## Related Skills\n\n- `@lint-and-validate` — Complementary: run after logic-lens for style\u002Fsyntax\n- `@security-auditor` — Specialized security-only deep scan\n- `@debugging-strategies` — Use when logic-lens findings need tracing\n\n## Additional Resources\n\n- [GitHub Repository](https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Flogic-lens)\n- [Dev.to Article: Why AI Code Review Misses the Most Dangerous Bugs](https:\u002F\u002Fdev.to\u002Fhyhmrright\u002Fwhy-ai-code-review-misses-the-most-dangerous-bugs-logic-lens-fixes-that-4a8l)\n- [Claude Code Skills Documentation](https:\u002F\u002Fdocs.anthropic.com\u002Fclaude-code)\n\n## Limitations\n\nUse this skill only when the task clearly matches the scope described above (code review and logic analysis). Logic Lens provides AI-powered analysis and should be combined with human review for production-critical decisions. Do not treat the output as a substitute for environment-specific testing or security audits.\n","# Logic Lens\n\n## Overview\n\nLogic Lens is a Claude Code skill that performs deep, logic-driven code review using formal reasoning frameworks. Unlike traditional linters that check syntax and style, Logic Lens analyzes your code for logical errors, race conditions, security vulnerabilities, type mismatches, and algorithmic flaws that only appear when you reason through the code's behavior.\n\nPowered by structured AI analysis, Logic Lens applies systematic logical inspection across 9 risk categories: null\u002Fundefined handling, type safety, concurrency, resource management, security injection, boundary conditions, algorithm correctness, state management, and API contract violations.\n\n## When to Use This Skill\n\n- Use when you want a thorough logic review before merging a PR\n- Use when a bug seems hard to find and standard linters aren't helping\n- Use when reviewing security-sensitive code paths (auth, payments, file access)\n- Use when refactoring complex business logic\n- Use when onboarding to a new codebase and need to understand risk areas\n\n## How It Works\n\nLogic Lens uses Claude Code's reasoning capabilities to:\n\n1. Parse code structure and build a mental model of data flow\n2. Apply formal logic checks across 9 risk categories\n3. Trace execution paths for edge cases and boundary conditions\n4. Identify security anti-patterns (injection, privilege escalation, data leakage)\n5. Report findings with severity levels and actionable fix suggestions\n\n## Installation\n\n```bash\n# Install via Claude Code plugin marketplace\n# Search: \"logic-lens\" in Claude Code > Extensions\n\n# Or install via NPX (Antigravity)\nnpx antigravity-awesome-skills --claude\n# Then invoke: @logic-lens\n```\n\n## Examples\n\n### Example 1: Review a Single File\n\n```\n@logic-lens review src\u002Fauth\u002Flogin.ts for security issues\n```\n\n**Logic Lens output:**\n```\n[CRITICAL] SQL Injection risk at line 42: user input concatenated into query string\n[HIGH] Missing rate limiting on login attempts\n[MEDIUM] Password comparison uses == instead of timing-safe comparison\n[LOW] Error messages may leak valid usernames (user enumeration)\n```\n\n### Example 2: Full Repository Scan\n\n```\n@logic-lens scan the entire codebase and prioritize by severity\n```\n\n### Example 3: Pre-PR Review\n\n```\n@logic-lens review all files changed in this branch before I open a PR\n```\n\n## The 9 Risk Categories\n\n| Category | What It Checks |\n|----------|----------------|\n| **Null\u002FUndefined** | Missing null checks, optional chaining gaps |\n| **Type Safety** | Implicit coercions, any-typed boundaries |\n| **Concurrency** | Race conditions, shared mutable state |\n| **Resource Management** | Unclosed handles, memory leaks |\n| **Security Injection** | SQL\u002FXSS\u002FCommand injection, path traversal |\n| **Boundary Conditions** | Off-by-one errors, integer overflow |\n| **Algorithm Correctness** | Wrong complexity, incorrect assumptions |\n| **State Management** | Inconsistent state, missing rollbacks |\n| **API Contracts** | Undocumented side effects, broken interfaces |\n\n## Best Practices\n\n- Run `@logic-lens` on authentication and payment code before every release\n- Combine with `@lint-and-validate` for full coverage: style + logic\n- Review the CRITICAL and HIGH findings first; LOW findings can be deferred\n- Use `@logic-lens` on legacy code you are about to modify to understand risk surface\n\n## Benchmark Results\n\nLogic Lens was tested against real-world codebases and caught issues missed by ESLint, TypeScript strict mode, and Snyk:\n\n- **47% of critical bugs** found were invisible to linters\n- **Race conditions** detected in async code that static analysis missed\n- **Security vulnerabilities** identified before deployment in CI pipeline\n\n## Related Skills\n\n- `@lint-and-validate` — Complementary: run after logic-lens for style\u002Fsyntax\n- `@security-auditor` — Specialized security-only deep scan\n- `@debugging-strategies` — Use when logic-lens findings need tracing\n\n## Additional Resources\n\n- [GitHub Repository](https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Flogic-lens)\n- [Dev.to Article: Why AI Code Review Misses the Most Dangerous Bugs](https:\u002F\u002Fdev.to\u002Fhyhmrright\u002Fwhy-ai-code-review-misses-the-most-dangerous-bugs-logic-lens-fixes-that-4a8l)\n- [Claude Code Skills Documentation](https:\u002F\u002Fdocs.anthropic.com\u002Fclaude-code)\n\n## Limitations\n\nUse this skill only when the task clearly matches the scope described above (code review and logic analysis). Logic Lens provides AI-powered analysis and should be combined with human review for production-critical decisions. Do not treat the output as a substitute for environment-specific testing or security audits.\n",{"name":5,"risk":41,"tags":48,"tools":51,"author":55,"source":32,"license":14,"category":56,"date_added":57,"description":7,"source_repo":58,"source_type":32,"license_source":59},[36,49,38,34,50],"logic-analysis","claude-code",[52,53,54,40],"claude","codex","cursor","hyhmrright","development","2026-04-29","hyhmrright\u002Flogic-lens","https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Flogic-lens\u002Fblob\u002Fmain\u002FLICENSE","cd2930847fb1ada3557e9207d3be0a1a1ed08f24","agent_skills\u002Flogic-lens",0,"https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid","2026-07-22 10:13:36",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add clodoaldoperito-droid\u002FARQUITETURA_JARVIS --skill logic-lens",{"tool":72,"command":73},"bunx","bunx skills add clodoaldoperito-droid\u002FARQUITETURA_JARVIS --skill logic-lens",{"tool":75,"command":76},"pnpm","pnpm dlx skills add clodoaldoperito-droid\u002FARQUITETURA_JARVIS --skill logic-lens","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fagent_skills\u002Flogic-lens\u002FSKILL.md",true,[],[81,108,141,161,175,200],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":90,"publishedAt":43},"01M6Q6BV6JFVC1CHDVW58F63AB","plotly","Interactive visualization library. Use when you need hover info, zoom, pan, or web-embeddable charts. Best for dashboards, exploratory analysis, and presentations. For static publication figures use matplotlib or scientific-visualization.","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fskills_extracted\u002Fskills\u002Fskills\u002Fplotly\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",[83,91,92,93,94,95,96,97,98,99,100,101,102,35,103,104,105,106,107],"static","Charts","for","you","figures","zoom","scientific","info","use","interactive","dashboards","matplotlib","library","visualization","presentations","hover","web",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":122,"publishedAt":43},"01M6Q5YRJC1RTZ8A8FK6Q80SH1","native-data-fetching","Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, and Expo Router data loaders (useLoaderData).","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fskills_extracted\u002Fskills\u002Fskills\u002Fnative-data-fetching\u002FSKILL.md",[114,117],{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[123,124,125,126,127,128,38,129,130,131,132,133,134,135,136,99,137,138,139,140],"native","data fetching","data","native data fetching","react","fetch","error","caching","error handling","query","call","router","swr","api","expo router","request","implementing","support",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":148,"publishedAt":43},"01M6Q4PFYVRE7AE05V883QFD55","expo-tailwind-setup","Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fskills_extracted\u002Fskills\u002Fskills\u002Fexpo-tailwind-setup\u002FSKILL.md",[147],{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},[149,150,151,152,127,93,153,154,123,155,156,157,158,159,160],"setup","expo tailwind setup","Tailwind","expo","with","nativewind","Tailwind CSS","react-native","styling","up","SET","css",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":43},"01M6Q4PD3AAXFEKXEW225X0K00","expo-dev-client","Build and distribute Expo development clients locally or via TestFlight","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fskills_extracted\u002Fskills\u002Fskills\u002Fexpo-dev-client\u002FSKILL.md",[],[168,169,152,170,171,172,173,174,56],"expo dev client","dev","client","clients","via","distribute","build",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":184,"publishedAt":43},"01M6Q4P6HYVP8WJK2YTSHDZGWB","expo-cicd-workflows","Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI\u002FCD or workflows in an Expo or EAS context, mentions .eas\u002Fworkflows\u002F, or wants help with EAS build pipelines or deployment automation.","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fskills_extracted\u002Fskills\u002Fskills\u002Fexpo-cicd-workflows\u002FSKILL.md",[181],{"categoryNo":182,"categoryName":183,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[152,185,186,187,188,189,190,174,191,99,192,193,194,195,153,196,197,198,93,199],"cicd","expo cicd workflows","workflows","help","about","CI\u002FCD","files","read","projects","Bash","ci","deployment","automation","workflow","deployment automation",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":212,"publishedAt":43},"01M6Q4P2ZHG9BFXPT680RJ6ZVG","expo-api-routes","Guidelines for creating API routes in Expo Router with EAS Hosting","https:\u002F\u002Fgithub.com\u002Fclodoaldoperito-droid\u002FARQUITETURA_JARVIS\u002Fblob\u002Fmain\u002Fskills_extracted\u002Fskills\u002Fskills\u002Fexpo-api-routes\u002FSKILL.md",[206,209],{"categoryNo":207,"categoryName":208,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":210,"categoryName":211,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000030","开发工程师",[213,136,152,214,93,215,153,137,216,134],"expo api routes","guidelines","eas hosting","hosting"]