[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SN09657B3P1EP97S61ZD0":3,"skill-same:01M79SN09657B3P1EP97S61ZD0":64},{"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":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M79SN09657B3P1EP97S61ZD0","codebase-inspection",null,"Inspect codebases w\u002F pygount: LOC, languages, ratios.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fcodebase-inspection\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: codebase-inspection\ndescription: \"Inspect codebases w\u002F pygount: LOC, languages, ratios.\"\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [LOC, Code Analysis, pygount, Codebase, Metrics, Repository]\n    related_skills: [github]\nprerequisites:\n  commands: [pygount]\n---\n\n**Triggers:** codebase, lines of code, loc, language breakdown, repo stats, how many lines, analyze repo, inspect codebase, project stats\n\n# Codebase Inspection with pygount\n\nAnalyze repositories for lines of code, language breakdown, file counts, and code-vs-comment ratios using `pygount`.\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- User wants code-vs-comment ratios\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## 1. Basic Summary (Most Common)\n\nGet a full language breakdown with file counts, code lines, and comment lines:\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 take a very long time or hang.\n\n## 2. Common Folder Exclusions\n\nAdjust based on the project type:\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# General catch-all\n--folders-to-skip=\".git,node_modules,venv,.venv,__pycache__,.cache,dist,build,.next,.tox,vendor,third_party\"\n```\n\n## 3. Filter by Specific 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## 4. Detailed File-by-File Output\n\n```bash\n# Default format shows per-file breakdown\npygount --folders-to-skip=\".git,node_modules,venv\" .\n\n# Sort by code lines (pipe through sort)\npygount --folders-to-skip=\".git,node_modules,venv\" . | sort -t$'\\t' -k1 -nr | head -20\n```\n\n## 5. Output Formats\n\n```bash\n# Summary table (default recommendation)\npygount --format=summary .\n\n# JSON output for programmatic use\npygount --format=json .\n\n# Pipe-friendly: Language, file count, code, docs, empty, string\npygount --format=summary . 2>\u002Fdev\u002Fnull\n```\n\n## 6. Interpreting Results\n\nThe summary table columns:\n- **Language** — detected programming language\n- **Files** — number of files of that language\n- **Code** — lines of actual code (executable\u002Fdeclarative)\n- **Comment** — lines that are comments or documentation\n- **%** — percentage of total\n\nSpecial pseudo-languages:\n- `__empty__` — empty files\n- `__binary__` — binary files (images, compiled, etc.)\n- `__generated__` — auto-generated files (detected heuristically)\n- `__duplicate__` — files with identical content\n- `__unknown__` — unrecognized file types\n\n## Pitfalls\n\n1. **Always exclude .git, node_modules, venv** — without `--folders-to-skip`, pygount will crawl everything and may take minutes or hang on large dependency trees.\n2. **Markdown shows 0 code lines** — pygount classifies all Markdown content as comments, not code. This is expected behavior.\n3. **JSON files show low code counts** — pygount may count JSON lines conservatively. For accurate JSON line counts, use `wc -l` directly.\n4. **Large monorepos** — for very large repos, consider using `--suffix` to target specific languages rather than scanning everything.","**Triggers:** codebase, lines of code, loc, language breakdown, repo stats, how many lines, analyze repo, inspect codebase, project stats\n\n# Codebase Inspection with pygount\n\nAnalyze repositories for lines of code, language breakdown, file counts, and code-vs-comment ratios using `pygount`.\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- User wants code-vs-comment ratios\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## 1. Basic Summary (Most Common)\n\nGet a full language breakdown with file counts, code lines, and comment lines:\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 take a very long time or hang.\n\n## 2. Common Folder Exclusions\n\nAdjust based on the project type:\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# General catch-all\n--folders-to-skip=\".git,node_modules,venv,.venv,__pycache__,.cache,dist,build,.next,.tox,vendor,third_party\"\n```\n\n## 3. Filter by Specific 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## 4. Detailed File-by-File Output\n\n```bash\n# Default format shows per-file breakdown\npygount --folders-to-skip=\".git,node_modules,venv\" .\n\n# Sort by code lines (pipe through sort)\npygount --folders-to-skip=\".git,node_modules,venv\" . | sort -t$'\\t' -k1 -nr | head -20\n```\n\n## 5. Output Formats\n\n```bash\n# Summary table (default recommendation)\npygount --format=summary .\n\n# JSON output for programmatic use\npygount --format=json .\n\n# Pipe-friendly: Language, file count, code, docs, empty, string\npygount --format=summary . 2>\u002Fdev\u002Fnull\n```\n\n## 6. Interpreting Results\n\nThe summary table columns:\n- **Language** — detected programming language\n- **Files** — number of files of that language\n- **Code** — lines of actual code (executable\u002Fdeclarative)\n- **Comment** — lines that are comments or documentation\n- **%** — percentage of total\n\nSpecial pseudo-languages:\n- `__empty__` — empty files\n- `__binary__` — binary files (images, compiled, etc.)\n- `__generated__` — auto-generated files (detected heuristically)\n- `__duplicate__` — files with identical content\n- `__unknown__` — unrecognized file types\n\n## Pitfalls\n\n1. **Always exclude .git, node_modules, venv** — without `--folders-to-skip`, pygount will crawl everything and may take minutes or hang on large dependency trees.\n2. **Markdown shows 0 code lines** — pygount classifies all Markdown content as comments, not code. This is expected behavior.\n3. **JSON files show low code counts** — pygount may count JSON lines conservatively. For accurate JSON line counts, use `wc -l` directly.\n4. **Large monorepos** — for very large repos, consider using `--suffix` to target specific languages rather than scanning everything.",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":37,"description":7,"prerequisites":41},"Hermes Agent","1.0.0",{"hermes":27},{"tags":28,"related_skills":35},[29,30,31,32,33,34],"LOC","Code Analysis","pygount","Codebase","Metrics","Repository",[36],"github",[38,39,40],"linux","macos","windows",{"commands":42},[31],"main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fcodebase-inspection","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill codebase-inspection",{"tool":56,"command":57},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill codebase-inspection",{"tool":59,"command":60},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill codebase-inspection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fcodebase-inspection\u002FSKILL.md",true,[],[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]