[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF3M94C47S2FQMT24F6WBT":3,"skill-same:01M6AF3M94C47S2FQMT24F6WBT":69},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6AF3M94C47S2FQMT24F6WBT","commit-smart",null,"Analyze staged\u002Funstaged changes and create semantic conventional commits with context about WHY, not just WHAT. Auto-detects commit type and scope from the diff. Supports optional type\u002Fscope arguments. Usage - \u002Fcommit-smart, \u002Fcommit-smart fix, \u002Fcommit-smart refactor api","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fgit\u002Fcommit-smart\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"commit smart","commit","diff","staged","changes","usage","with","about","unstaged","scope","type","conventional commits","auto","fix","just","analyze","commits","why","api","refactor","create","2026-11-10 10:12:30",false,"---\nname: commit-smart\ndescription: Analyze staged\u002Funstaged changes and create semantic conventional commits with context about WHY, not just WHAT. Auto-detects commit type and scope from the diff. Supports optional type\u002Fscope arguments. Usage - \u002Fcommit-smart, \u002Fcommit-smart fix, \u002Fcommit-smart refactor api\n---\n\n# Smart Commit\n\nCreate meaningful conventional commits by analyzing your actual changes.\n\n## Workflow\n\n### Step 1: Assess the working tree\n\nRun these commands to understand the current state:\n\n```bash\ngit status\ngit diff --stat\ngit diff --cached --stat\n```\n\n### Step 2: Handle unstaged changes\n\nIf nothing is staged (`git diff --cached` is empty):\n\n1. Show the user what files have changed\n2. Suggest what to stage based on logical grouping (e.g., \"these 3 files are all related to the auth refactor\")\n3. Ask if they want to stage all, or select specific files\n4. Stage the approved files with `git add \u003Cfiles>`\n\nIf changes are already staged, proceed to analysis.\n\n### Step 3: Analyze the diff\n\nRead the full staged diff:\n\n```bash\ngit diff --cached\n```\n\nDetermine the commit type from the changes:\n\n| Signal | Type |\n|--------|------|\n| New files with new functionality | `feat` |\n| New test files or test additions | `test` |\n| Changes to existing logic fixing incorrect behavior | `fix` |\n| Structural changes without behavior change | `refactor` |\n| package.json, tsconfig, CI config changes | `chore` |\n| Build\u002Fbundler config changes | `build` |\n| README, docs, comments only | `docs` |\n| Formatting, whitespace, semicolons only | `style` |\n| Performance improvements | `perf` |\n\nDetermine the scope from the primary directory or module affected:\n- `src\u002Fapi\u002F` -> `api`\n- `src\u002Fcomponents\u002Fauth\u002F` -> `auth`\n- `tests\u002F` -> `tests`\n- Root config files -> omit scope\n- Multiple unrelated areas -> omit scope\n\n### Step 4: Check for user overrides\n\nIf the user provided arguments via `$ARGUMENTS`:\n- Single word (e.g., `fix`) -> use as commit type\n- Two words (e.g., `refactor api`) -> use as type and scope\n- Otherwise -> use auto-detected values\n\n### Step 5: Compose the commit message\n\nFormat: `type(scope): imperative short description`\n\nRules:\n- Subject line max 72 characters\n- Use imperative mood (\"add\", \"fix\", \"refactor\", not \"added\", \"fixes\")\n- Don't end with a period\n- Body explains **WHY** this change was made, not what changed (the diff shows what)\n- If changes are trivial (typo fix, formatting), skip the body\n\nExample:\n```\nfeat(auth): add JWT refresh token rotation\n\nTokens were expiring mid-session for users with slow connections.\nRotating refresh tokens extends the session without compromising\nsecurity, since each refresh token can only be used once.\n```\n\n### Step 6: Confirm and commit\n\nShow the user the proposed commit message and ask for confirmation.\n\nIf confirmed, run:\n```bash\ngit commit -m \"\u003Cmessage>\"\n```\n\nThen verify with:\n```bash\ngit log --oneline -1\n```\n\nShow the committed hash and message.\n\n## Tips\n\n- Run after completing a logical unit of work, not after every file change\n- If the diff is too large for one commit, suggest splitting into multiple commits\n- For breaking changes, add `!` after the scope: `feat(api)!: change response format`\n- The body should answer \"if someone reads this commit in 6 months, will they understand WHY?\"\n","# Smart Commit\n\nCreate meaningful conventional commits by analyzing your actual changes.\n\n## Workflow\n\n### Step 1: Assess the working tree\n\nRun these commands to understand the current state:\n\n```bash\ngit status\ngit diff --stat\ngit diff --cached --stat\n```\n\n### Step 2: Handle unstaged changes\n\nIf nothing is staged (`git diff --cached` is empty):\n\n1. Show the user what files have changed\n2. Suggest what to stage based on logical grouping (e.g., \"these 3 files are all related to the auth refactor\")\n3. Ask if they want to stage all, or select specific files\n4. Stage the approved files with `git add \u003Cfiles>`\n\nIf changes are already staged, proceed to analysis.\n\n### Step 3: Analyze the diff\n\nRead the full staged diff:\n\n```bash\ngit diff --cached\n```\n\nDetermine the commit type from the changes:\n\n| Signal | Type |\n|--------|------|\n| New files with new functionality | `feat` |\n| New test files or test additions | `test` |\n| Changes to existing logic fixing incorrect behavior | `fix` |\n| Structural changes without behavior change | `refactor` |\n| package.json, tsconfig, CI config changes | `chore` |\n| Build\u002Fbundler config changes | `build` |\n| README, docs, comments only | `docs` |\n| Formatting, whitespace, semicolons only | `style` |\n| Performance improvements | `perf` |\n\nDetermine the scope from the primary directory or module affected:\n- `src\u002Fapi\u002F` -> `api`\n- `src\u002Fcomponents\u002Fauth\u002F` -> `auth`\n- `tests\u002F` -> `tests`\n- Root config files -> omit scope\n- Multiple unrelated areas -> omit scope\n\n### Step 4: Check for user overrides\n\nIf the user provided arguments via `$ARGUMENTS`:\n- Single word (e.g., `fix`) -> use as commit type\n- Two words (e.g., `refactor api`) -> use as type and scope\n- Otherwise -> use auto-detected values\n\n### Step 5: Compose the commit message\n\nFormat: `type(scope): imperative short description`\n\nRules:\n- Subject line max 72 characters\n- Use imperative mood (\"add\", \"fix\", \"refactor\", not \"added\", \"fixes\")\n- Don't end with a period\n- Body explains **WHY** this change was made, not what changed (the diff shows what)\n- If changes are trivial (typo fix, formatting), skip the body\n\nExample:\n```\nfeat(auth): add JWT refresh token rotation\n\nTokens were expiring mid-session for users with slow connections.\nRotating refresh tokens extends the session without compromising\nsecurity, since each refresh token can only be used once.\n```\n\n### Step 6: Confirm and commit\n\nShow the user the proposed commit message and ask for confirmation.\n\nIf confirmed, run:\n```bash\ngit commit -m \"\u003Cmessage>\"\n```\n\nThen verify with:\n```bash\ngit log --oneline -1\n```\n\nShow the committed hash and message.\n\n## Tips\n\n- Run after completing a logical unit of work, not after every file change\n- If the diff is too large for one commit, suggest splitting into multiple commits\n- For breaking changes, add `!` after the scope: `feat(api)!: change response format`\n- The body should answer \"if someone reads this commit in 6 months, will they understand WHY?\"\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fgit\u002Fcommit-smart",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add davila7\u002Fclaude-code-templates --skill commit-smart",{"tool":61,"command":62},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill commit-smart",{"tool":64,"command":65},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill commit-smart","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fgit\u002Fcommit-smart\u002FSKILL.md",true,[],[70,101,128,160,195,219],{"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":81,"publishedAt":40},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[82,83,84,85,86,87,88,89,90,91,92,25,93,94,95,96,97,98,99,100],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","use","when","reduce","record","track","verdict","evm","solana","how","public","look",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":108,"publishedAt":40},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[107],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[109,110,111,112,113,114,115,116,117,118,119,91,120,121,122,123,124,125,126,127],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":143,"publishedAt":40},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[134,137,138],{"categoryNo":135,"categoryName":136,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[144,145,146,147,148,149,150,87,151,152,33,153,154,155,156,90,157,158,91,159],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","tool","calls","only","MCP","access","database","query",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":164,"licenseFileUrl":165,"sourceHtmlUrl":166,"categories":167,"keywords":171,"publishedAt":40},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000009","前端开发",[172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,87,194],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":164,"licenseFileUrl":199,"sourceHtmlUrl":200,"categories":201,"keywords":206,"publishedAt":40},"01M6AFWF33SFV9Z3SF4PEEE4BF","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\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[202,205],{"categoryNo":203,"categoryName":204,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":169,"categoryName":170,"taxonomyType":79,"taxonomyTypeDesc":80},[207,208,209,210,211,173,212,182,183,213,214,215,216,87,217,25,218],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":164,"licenseFileUrl":223,"sourceHtmlUrl":224,"categories":225,"keywords":233,"publishedAt":40},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[226,229,230],{"categoryNo":227,"categoryName":228,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":231,"categoryName":232,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000036","内容创作者",[234,235,236,237,238,239,240,241,175,242,185,120,243,244,245,246,247,155,248,91,249,250,251,252,253,98,254],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]