[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JF1FJDEC1AB79EVCQ9MSH8":3,"skill-same:01M6JF1FJDEC1AB79EVCQ9MSH8":83},{"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":27,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":68,"install":69,"resources":82},"01M6JF1FJDEC1AB79EVCQ9MSH8","code-quality",null,"Code quality and verification: codebase metrics, post-implementation cleanup, and pre-commit verification pipeline.","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fops\u002Fcode-quality\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[28,29,30,31,32,33,34,5,35,36,37,38,39,40,41,42,43,44,45,46],"quality","code quality","code","verification","development-workflow","test-driven-development","linting","analysis","pipeline","static-analysis","metrics","macos","code-review","cleanup","windows","commit","workflow","security","review","2026-11-10 10:12:30",false,"---\nname: code-quality\ndescription: \"Code quality and verification: codebase metrics, post-implementation cleanup, and pre-commit verification pipeline.\"\nversion: 1.0.0\nauthor: Hermes Agent Curator\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [code-quality, code-review, verification, metrics, static-analysis, linting, security, cleanup]\n    related_skills: [test-driven-development, development-workflow, github-code-review]\n---\n\n# Code Quality & Verification\n\nThree complementary tools for ensuring code quality at different stages of development:\n\n| Mode | When | Tool | What it does |\n|------|------|------|-------------|\n| **Codebase Metrics** | Explore\u002Fadopt a repo | `pygount` | Analyze LOC, language breakdown, code-vs-comment ratios |\n| **Simplify Code** | After implementing changes | 3 parallel subagents | Clean up recent changes for reuse, quality, efficiency |\n| **Pre-Commit Verification** | Before `git commit` | Automated pipeline | Security scan, quality gates, independent reviewer, auto-fix |\n\n---\n\n## Section 1: Codebase Metrics (pygount)\n\nAnalyze repositories for lines of code, language breakdown, file counts, and code-vs-comment ratios.\n\n### When to Use\n\n- User asks for LOC (lines of code) count\n- User wants a language breakdown of a repo\n- User asks about codebase size or composition\n- General \"how big is this repo\" questions\n\n### Prerequisites\n\n```bash\npip install --break-system-packages pygount 2>\u002Fdev\u002Fnull || pip install pygount\n```\n\n### Basic Summary\n\n```bash\ncd \u002Fpath\u002Fto\u002Frepo\npygount --format=summary \\\n  --folders-to-skip=\".git,node_modules,venv,.venv,__pycache__,.cache,dist,build,.next,.tox,.eggs,*.egg-info\" \\\n  .\n```\n\n**IMPORTANT:** Always use `--folders-to-skip` to exclude dependency\u002Fbuild directories, otherwise pygount will crawl them and hang.\n\n### Common Folder Exclusions\n\n```bash\n# Python projects\n--folders-to-skip=\".git,venv,.venv,__pycache__,.cache,dist,build,.tox,.eggs,.mypy_cache\"\n\n# JavaScript\u002FTypeScript projects\n--folders-to-skip=\".git,node_modules,dist,build,.next,.cache,.turbo,coverage\"\n```\n\n### Filter by Language\n\n```bash\n# Only count Python files\npygount --suffix=py --format=summary .\n\n# Only count Python and YAML\npygount --suffix=py,yaml,yml --format=summary .\n```\n\n### Output Formats\n\n```bash\npygount --format=summary .        # Summary table\npygount --format=json .           # JSON for programmatic use\n```\n\n### Interpreting Results\n\nThe summary table columns: **Language**, **Files**, **Code** (executable lines), **Comment** (documentation lines), **%** (percentage of total).\n\nSpecial pseudo-languages: `__empty__` (empty files), `__binary__` (binary), `__generated__` (auto-generated), `__duplicate__` (identical content), `__unknown__` (unrecognized types).\n\n### Pitfalls\n\n1. **Always exclude .git, node_modules, venv** — without `--folders-to-skip`, pygount crawls everything and may hang\n2. **Markdown shows 0 code lines** — pygount classifies all Markdown as comments, not code (expected)\n3. **JSON files show low code counts** — use `wc -l` for accurate JSON line counts\n4. **Large monorepos** — use `--suffix` to target specific languages rather than scanning everything\n\n---\n\n## Section 2: Simplify Code — Parallel Review & Cleanup\n\nReview recent code changes with three focused reviewers running in parallel, aggregate findings, and apply fixes.\n\n**Core principle:** Three narrow reviewers beat one broad reviewer. Each deeply searches the codebase for a single class of problem.\n\n### When to Use\n\n- \"simplify\" \u002F \"simplify my changes\" \u002F \"review my code\"\n- \"\u002Fsimplify\" (Claude Code habit)\n\nOptional modifiers: **Focus** (reuse\u002Fquality\u002Fefficiency), **Dry run** (report only), **Scope** (last commit \u002F staged \u002F specific file)\n\n### Phase 1 — Identify Changes\n\n```bash\n# Default: uncommitted working-tree changes\ngit diff\n\n# If empty, include staged\ngit diff HEAD\n\n# Scoped variants:\ngit diff --staged              # staged changes\ngit diff HEAD~1                # last commit\ngit diff main...HEAD           # this branch\u002FPR\ngit diff -- src\u002Ffoo.py         # specific file\n```\n\n### Phase 2 — Launch Three Reviewers\n\nUse `delegate_task` **batch mode** — pass all three tasks in one `tasks` array:\n\n**Reviewer 1 — Code Reuse:** Search for code that duplicates existing functionality. Check utility modules, shared helpers, adjacent files for existing functions to reuse.\n\n**Reviewer 2 — Code Quality:** Look for redundant state, parameter sprawl, copy-paste-with-variation, leaky abstractions, stringly-typed code.\n\n**Reviewer 3 — Efficiency:** Look for unnecessary work, missed concurrency, hot-path bloat, TOCTOU anti-patterns, memory issues, overly broad reads.\n\nEach gets the **complete diff** plus repo path and toolsets `[terminal, file, search]`.\n\n### Phase 3 — Aggregate and Apply\n\n1. Merge findings, dedup overlaps\n2. Discard false positives\n3. Resolve conflicts: **correctness > user's focus > readability > micro-perf**\n4. Apply fixes with `patch`\u002F`write_file` (or dry run)\n5. Verify: run targeted tests + linter\n6. Summarize what changed and what was skipped\n\n### Pitfalls\n\n- Don't fan out wider than ~3 reviewers\n- Give the **WHOLE diff** to each reviewer\n- Require `file:line` evidence from reviewers\n- Keep edits scoped to what the diff touched\n- Check AGENTS.md \u002F CLAUDE.md for project conventions\n\n---\n\n## Section 3: Pre-Commit Verification\n\nAutomated verification pipeline before code lands. Static scans, baseline-aware quality gates, an independent reviewer subagent, and an auto-fix loop.\n\n**Core principle:** No agent should verify its own work. Fresh context finds what you miss.\n\n### When to Use\n\n- After implementing a feature or bug fix, before `git commit` or `git push`\n- When user says \"commit\", \"push\", \"ship\", \"done\", \"verify\", or \"review before merge\"\n- After completing a task with 2+ file edits in a git repo\n\n**Skip for:** documentation-only changes, pure config tweaks, or explicit \"skip verification\".\n\n### Step 1 — Get the Diff\n\n```bash\ngit diff --cached\n```\n\nIf empty, try `git diff` then `git diff HEAD~1 HEAD`. If diff exceeds 15K chars, split by file.\n\n### Step 2 — Static Security Scan\n\nScan added lines for hardcoded secrets, shell injection, dangerous eval\u002Fexec, unsafe deserialization, SQL injection:\n\n```bash\ngit diff --cached | grep \"^+\" | grep -iE \"(api_key|secret|password|token|passwd)\\s*=\\s*['\\\"][^'\\\"]{6,}['\\\"]\"\ngit diff --cached | grep \"^+\" | grep -E \"os\\.system\\(|subprocess.*shell=True\"\ngit diff --cached | grep \"^+\" | grep -E \"\\beval\\(|\\bexec\\(\"\ngit diff --cached | grep \"^+\" | grep -E \"pickle\\.loads?\\(\"\ngit diff --cached | grep \"^+\" | grep -E \"execute\\(f\\\"|\\.format\\(.*SELECT|\\.format\\(.*INSERT\"\n```\n\n### Step 3 — Baseline Tests and Linting\n\nDetect the project language and run appropriate tools. Capture baseline BEFORE changes (stash changes, run, pop). Only NEW failures block commit.\n\n**Test frameworks** (auto-detect):\n```bash\npython -m pytest --tb=no -q 2>&1 | tail -5\nnpm test -- --passWithNoTests 2>&1 | tail -5\ncargo test 2>&1 | tail -5\ngo test .\u002F... 2>&1 | tail -5\n```\n","# Code Quality & Verification\n\nThree complementary tools for ensuring code quality at different stages of development:\n\n| Mode | When | Tool | What it does |\n|------|------|------|-------------|\n| **Codebase Metrics** | Explore\u002Fadopt a repo | `pygount` | Analyze LOC, language breakdown, code-vs-comment ratios |\n| **Simplify Code** | After implementing changes | 3 parallel subagents | Clean up recent changes for reuse, quality, efficiency |\n| **Pre-Commit Verification** | Before `git commit` | Automated pipeline | Security scan, quality gates, independent reviewer, auto-fix |\n\n---\n\n## Section 1: Codebase Metrics (pygount)\n\nAnalyze repositories for lines of code, language breakdown, file counts, and code-vs-comment ratios.\n\n### When to Use\n\n- User asks for LOC (lines of code) count\n- User wants a language breakdown of a repo\n- User asks about codebase size or composition\n- General \"how big is this repo\" questions\n\n### Prerequisites\n\n```bash\npip install --break-system-packages pygount 2>\u002Fdev\u002Fnull || pip install pygount\n```\n\n### Basic Summary\n\n```bash\ncd \u002Fpath\u002Fto\u002Frepo\npygount --format=summary \\\n  --folders-to-skip=\".git,node_modules,venv,.venv,__pycache__,.cache,dist,build,.next,.tox,.eggs,*.egg-info\" \\\n  .\n```\n\n**IMPORTANT:** Always use `--folders-to-skip` to exclude dependency\u002Fbuild directories, otherwise pygount will crawl them and hang.\n\n### Common Folder Exclusions\n\n```bash\n# Python projects\n--folders-to-skip=\".git,venv,.venv,__pycache__,.cache,dist,build,.tox,.eggs,.mypy_cache\"\n\n# JavaScript\u002FTypeScript projects\n--folders-to-skip=\".git,node_modules,dist,build,.next,.cache,.turbo,coverage\"\n```\n\n### Filter by Language\n\n```bash\n# Only count Python files\npygount --suffix=py --format=summary .\n\n# Only count Python and YAML\npygount --suffix=py,yaml,yml --format=summary .\n```\n\n### Output Formats\n\n```bash\npygount --format=summary .        # Summary table\npygount --format=json .           # JSON for programmatic use\n```\n\n### Interpreting Results\n\nThe summary table columns: **Language**, **Files**, **Code** (executable lines), **Comment** (documentation lines), **%** (percentage of total).\n\nSpecial pseudo-languages: `__empty__` (empty files), `__binary__` (binary), `__generated__` (auto-generated), `__duplicate__` (identical content), `__unknown__` (unrecognized types).\n\n### Pitfalls\n\n1. **Always exclude .git, node_modules, venv** — without `--folders-to-skip`, pygount crawls everything and may hang\n2. **Markdown shows 0 code lines** — pygount classifies all Markdown as comments, not code (expected)\n3. **JSON files show low code counts** — use `wc -l` for accurate JSON line counts\n4. **Large monorepos** — use `--suffix` to target specific languages rather than scanning everything\n\n---\n\n## Section 2: Simplify Code — Parallel Review & Cleanup\n\nReview recent code changes with three focused reviewers running in parallel, aggregate findings, and apply fixes.\n\n**Core principle:** Three narrow reviewers beat one broad reviewer. Each deeply searches the codebase for a single class of problem.\n\n### When to Use\n\n- \"simplify\" \u002F \"simplify my changes\" \u002F \"review my code\"\n- \"\u002Fsimplify\" (Claude Code habit)\n\nOptional modifiers: **Focus** (reuse\u002Fquality\u002Fefficiency), **Dry run** (report only), **Scope** (last commit \u002F staged \u002F specific file)\n\n### Phase 1 — Identify Changes\n\n```bash\n# Default: uncommitted working-tree changes\ngit diff\n\n# If empty, include staged\ngit diff HEAD\n\n# Scoped variants:\ngit diff --staged              # staged changes\ngit diff HEAD~1                # last commit\ngit diff main...HEAD           # this branch\u002FPR\ngit diff -- src\u002Ffoo.py         # specific file\n```\n\n### Phase 2 — Launch Three Reviewers\n\nUse `delegate_task` **batch mode** — pass all three tasks in one `tasks` array:\n\n**Reviewer 1 — Code Reuse:** Search for code that duplicates existing functionality. Check utility modules, shared helpers, adjacent files for existing functions to reuse.\n\n**Reviewer 2 — Code Quality:** Look for redundant state, parameter sprawl, copy-paste-with-variation, leaky abstractions, stringly-typed code.\n\n**Reviewer 3 — Efficiency:** Look for unnecessary work, missed concurrency, hot-path bloat, TOCTOU anti-patterns, memory issues, overly broad reads.\n\nEach gets the **complete diff** plus repo path and toolsets `[terminal, file, search]`.\n\n### Phase 3 — Aggregate and Apply\n\n1. Merge findings, dedup overlaps\n2. Discard false positives\n3. Resolve conflicts: **correctness > user's focus > readability > micro-perf**\n4. Apply fixes with `patch`\u002F`write_file` (or dry run)\n5. Verify: run targeted tests + linter\n6. Summarize what changed and what was skipped\n\n### Pitfalls\n\n- Don't fan out wider than ~3 reviewers\n- Give the **WHOLE diff** to each reviewer\n- Require `file:line` evidence from reviewers\n- Keep edits scoped to what the diff touched\n- Check AGENTS.md \u002F CLAUDE.md for project conventions\n\n---\n\n## Section 3: Pre-Commit Verification\n\nAutomated verification pipeline before code lands. Static scans, baseline-aware quality gates, an independent reviewer subagent, and an auto-fix loop.\n\n**Core principle:** No agent should verify its own work. Fresh context finds what you miss.\n\n### When to Use\n\n- After implementing a feature or bug fix, before `git commit` or `git push`\n- When user says \"commit\", \"push\", \"ship\", \"done\", \"verify\", or \"review before merge\"\n- After completing a task with 2+ file edits in a git repo\n\n**Skip for:** documentation-only changes, pure config tweaks, or explicit \"skip verification\".\n\n### Step 1 — Get the Diff\n\n```bash\ngit diff --cached\n```\n\nIf empty, try `git diff` then `git diff HEAD~1 HEAD`. If diff exceeds 15K chars, split by file.\n\n### Step 2 — Static Security Scan\n\nScan added lines for hardcoded secrets, shell injection, dangerous eval\u002Fexec, unsafe deserialization, SQL injection:\n\n```bash\ngit diff --cached | grep \"^+\" | grep -iE \"(api_key|secret|password|token|passwd)\\s*=\\s*['\\\"][^'\\\"]{6,}['\\\"]\"\ngit diff --cached | grep \"^+\" | grep -E \"os\\.system\\(|subprocess.*shell=True\"\ngit diff --cached | grep \"^+\" | grep -E \"\\beval\\(|\\bexec\\(\"\ngit diff --cached | grep \"^+\" | grep -E \"pickle\\.loads?\\(\"\ngit diff --cached | grep \"^+\" | grep -E \"execute\\(f\\\"|\\.format\\(.*SELECT|\\.format\\(.*INSERT\"\n```\n\n### Step 3 — Baseline Tests and Linting\n\nDetect the project language and run appropriate tools. Capture baseline BEFORE changes (stash changes, run, pop). Only NEW failures block commit.\n\n**Test frameworks** (auto-detect):\n```bash\npython -m pytest --tb=no -q 2>&1 | tail -5\nnpm test -- --passWithNoTests 2>&1 | tail -5\ncargo test 2>&1 | tail -5\ngo test .\u002F... 2>&1 | tail -5\n```\n",{"name":5,"author":52,"license":14,"version":53,"metadata":54,"platforms":59,"description":7},"Hermes Agent Curator","1.0.0",{"hermes":55},{"tags":56,"related_skills":57},[5,40,31,38,37,34,45,41],[33,32,58],"github-code-review",[60,39,42],"linux","master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fops\u002Fcode-quality",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add S3YED\u002Fappie-kit --skill code-quality",{"tool":75,"command":76},"bunx","bunx skills add S3YED\u002Fappie-kit --skill code-quality",{"tool":78,"command":79},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill code-quality","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fops\u002Fcode-quality\u002FSKILL.md",true,[],[84,116,149,175,203,223],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":97,"publishedAt":47},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[90,93,96],{"categoryNo":91,"categoryName":92,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":94,"categoryName":95,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115],"music","ai music","humanizer","visualization","Tools","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":128,"publishedAt":47},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":126,"categoryName":127,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000032","设计师",[129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":157,"publishedAt":47},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[155,156],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":126,"categoryName":127,"taxonomyType":25,"taxonomyTypeDesc":26},[130,158,134,159,160,161,136,162,163,164,165,166,167,168,169,170,171,172,173,174],"elements","agentic webdesign agent elements","MCP","ai agent","registry","search","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock","source",{"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":185,"publishedAt":47},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[181,184],{"categoryNo":182,"categoryName":183,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[186,187,188,39,189,60,42,190,191,192,193,194,195,196,197,198,199,200,201,202],"deployment","vercel deployment","vercel","cli","deploy","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":210,"publishedAt":47},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[209],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[211,28,212,213,46,214,44,43,215,30,216,217,218,219,220,221,222],"workflows","software","software quality workflows","tdd","debugging","debugger","pre-commit","investigation","code simplification","user","simplification","for",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":227,"categories":228,"keywords":236,"publishedAt":47},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[229,232,235],{"categoryNo":230,"categoryName":231,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":233,"categoryName":234,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[237,238,239,240,241,242,243,244,39,245,246,136,247,42,248,30,249,250,251,33],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","writing","safe","typescript","react components","modular","refactor","simplify","patterns"]