[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMRZ1XYPZTCWJ3KSS7N5T3":3,"skill-same:01M7DMRZ1XYPZTCWJ3KSS7N5T3":63},{"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":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7DMRZ1XYPZTCWJ3KSS7N5T3","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.","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Flogic-lens\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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":24,"tags":25,"tools":31,"author":36,"source":37,"license":15,"category":38,"date_added":39,"description":7,"source_repo":40,"source_type":37,"license_source":41},"safe",[26,27,28,29,30],"code-review","logic-analysis","debugging","security-review","claude-code",[32,33,34,35],"claude","codex","cursor","gemini","hyhmrright","community","development","2026-04-29","hyhmrright\u002Flogic-lens","https:\u002F\u002Fgithub.com\u002Fhyhmrright\u002Flogic-lens\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Flogic-lens",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill logic-lens",{"tool":55,"command":56},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill logic-lens",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill logic-lens","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Flogic-lens\u002FSKILL.md",true,[],[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]