[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79F2STM46DHMTSJAGQ6D5VV":3,"skill-same:01M79F2STM46DHMTSJAGQ6D5VV":51},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M79F2STM46DHMTSJAGQ6D5VV","analyze-codebase-improvements",null,"Read-only repo audit: maintainability, correctness, tests, docs, deps, perf.","BumpyClock\u002Fagent-templates","BumpyClock","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1883824?v=4","01M79EW0FDP9MFXH1FKH800S7T","Aditya Sharma","01M79EW0G27TTKZWTFQ8W5HVB4",2,"MIT","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fanalyze-codebase-improvements\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analyze-codebase-improvements\ndescription: \"Read-only repo audit: maintainability, correctness, tests, docs, deps, perf.\"\n---\n\n# Analyze Codebase Improvements\n\nRead-only repo audit. Do not edit code.\n\n## Inputs\n\n- Scope: paths\u002Fglobs\u002Fdirs. Default: whole repo.\n- Focus: `architecture`, `complexity`, `time-complexity`, `duplication`, `dead-code`, `legacy-code`, `tests`, `errors`, `types`, `comments`, `docs`, `deps`, `simplify`, `all`. Default: `all`.\n\n## Workflow\n\n1. Read repo docs\u002Flocal instructions first.\n2. Parse scope\u002Ffocus. Exclude generated, vendored, build, lockfile-only areas unless asked.\n3. Map repo shape: dirs, languages, frameworks, tooling, hotspots, large\u002Fstale areas.\n4. Pick lenses from focus. Use subagents when allowed\u002Fuseful; shard by subsystem or concern.\n5. For every finding: cite files\u002Fsymbols, evidence, failure mode or maintenance cost, smallest viable change.\n6. Merge duplicates. Drop speculative\u002Fstyle-only\u002Flow-signal items.\n7. Rank by impact, effort, confidence, regression risk.\n8. For `comments`, `docs`, or `all`: use `technical-writer` if available; otherwise audit locally.\n\n## Lenses\n\n- Architecture: boundaries, ownership, coupling, layering.\n- Complexity\u002Fsimplify: hard control flow, oversized files, needless abstraction, smaller equivalent code.\n- Deletion\u002Fdeps\u002Fdead-code: unused files, stale abstractions, removable paths, unused\u002Foutdated\u002Foverlapping deps.\n- Time complexity: hot loops, repeated scans\u002Flookups\u002Fsorts\u002Fallocations\u002Frecompute; include current complexity, bottleneck, lower-complexity alternative, expected complexity, space\u002Freadability trade-off, worth doing.\n- Duplication\u002Flegacy: copy-paste, near-duplicate modules, compatibility bridges, old patterns, hard-coded values, orphan flows.\n- Tests: missing coverage, weak assertions, risky untested behavior.\n- Errors: silent failures, swallowed exceptions, weak reporting.\n- Types: weak invariants, leaky models, unclear boundaries.\n- Comments\u002Fdocs: stale\u002Fmisleading\u002Fredundant comments, missing durable docs, setup\u002FAPI\u002Fcontributor drift. Validate comment accuracy and language docs standards: JSDoc\u002FTSDoc, docstrings, Go doc, rustdoc, DocC.\n\nDeletion-first tags for complexity\u002Fdeps\u002Fdead-code\u002Fsimplify findings:\n\n- `delete:` dead code, unused flexibility, speculative feature. Replacement: nothing.\n- `stdlib:` hand-rolled code stdlib already covers. Name API.\n- `native:` dependency\u002Fcustom code platform\u002Fframework\u002FDB\u002Fbrowser\u002FOS already covers. Name feature.\n- `yagni:` abstraction\u002Fconfig\u002Flayer with one impl, no real caller, or unproven need.\n- `shrink:` same behavior with fewer concepts\u002Flines. Show shorter replacement when concise.\n\n## Rules\n\n- Analysis only; no code edits.\n- Prefer high-leverage findings over exhaustive nitpicks.\n- Favor deletion\u002Fsimplification over new abstraction.\n- Prefer stdlib, native features, and existing deps over custom code\u002Fnew deps.\n- For over-engineering, name what to cut and what replaces it; include `net: -N lines possible` when meaningful and cheap.\n- Correctness, tests, docs, deps, and perf gaps still count even when line count grows or does not shrink.\n- Do not chase tiny line cuts that obscure behavior or fight repo conventions.\n- Validate against existing patterns\u002Flocal rules.\n- Separate quick wins from strategic refactors.\n- Report uncertainty when confidence low.\n- Do not force optimization when asymptotic win\u002Ftrade-off is poor.\n- If nothing useful to cut in simplify-only pass, say lean already.\n\n## Output\n\n```markdown\n# Codebase Improvement Summary\n\n## Executive Summary\n- 2-4 sentences: health + biggest opportunities\n\n## Top Improvements To Make Now\n- [Impact | Effort | Confidence] Title\n  - Files\u002FSymbols:\n  - Evidence:\n  - Smallest viable change:\n  - Why now:\n\n## Quick Wins\n- Low-risk, high-leverage cleanups\n\n## Strategic Refactors\n- Larger changes needing planning\n\n## Deletion \u002F De-scope Opportunities\n- Code, configs, abstractions, or deps likely removable\n\n## Test \u002F Docs \u002F Dependency Gaps\n- Missing coverage, stale docs, missing API docs, toolchain cleanup\n\n## Questions \u002F Assumptions\n- Uncertainties needing confirmation\n```\n","# Analyze Codebase Improvements\n\nRead-only repo audit. Do not edit code.\n\n## Inputs\n\n- Scope: paths\u002Fglobs\u002Fdirs. Default: whole repo.\n- Focus: `architecture`, `complexity`, `time-complexity`, `duplication`, `dead-code`, `legacy-code`, `tests`, `errors`, `types`, `comments`, `docs`, `deps`, `simplify`, `all`. Default: `all`.\n\n## Workflow\n\n1. Read repo docs\u002Flocal instructions first.\n2. Parse scope\u002Ffocus. Exclude generated, vendored, build, lockfile-only areas unless asked.\n3. Map repo shape: dirs, languages, frameworks, tooling, hotspots, large\u002Fstale areas.\n4. Pick lenses from focus. Use subagents when allowed\u002Fuseful; shard by subsystem or concern.\n5. For every finding: cite files\u002Fsymbols, evidence, failure mode or maintenance cost, smallest viable change.\n6. Merge duplicates. Drop speculative\u002Fstyle-only\u002Flow-signal items.\n7. Rank by impact, effort, confidence, regression risk.\n8. For `comments`, `docs`, or `all`: use `technical-writer` if available; otherwise audit locally.\n\n## Lenses\n\n- Architecture: boundaries, ownership, coupling, layering.\n- Complexity\u002Fsimplify: hard control flow, oversized files, needless abstraction, smaller equivalent code.\n- Deletion\u002Fdeps\u002Fdead-code: unused files, stale abstractions, removable paths, unused\u002Foutdated\u002Foverlapping deps.\n- Time complexity: hot loops, repeated scans\u002Flookups\u002Fsorts\u002Fallocations\u002Frecompute; include current complexity, bottleneck, lower-complexity alternative, expected complexity, space\u002Freadability trade-off, worth doing.\n- Duplication\u002Flegacy: copy-paste, near-duplicate modules, compatibility bridges, old patterns, hard-coded values, orphan flows.\n- Tests: missing coverage, weak assertions, risky untested behavior.\n- Errors: silent failures, swallowed exceptions, weak reporting.\n- Types: weak invariants, leaky models, unclear boundaries.\n- Comments\u002Fdocs: stale\u002Fmisleading\u002Fredundant comments, missing durable docs, setup\u002FAPI\u002Fcontributor drift. Validate comment accuracy and language docs standards: JSDoc\u002FTSDoc, docstrings, Go doc, rustdoc, DocC.\n\nDeletion-first tags for complexity\u002Fdeps\u002Fdead-code\u002Fsimplify findings:\n\n- `delete:` dead code, unused flexibility, speculative feature. Replacement: nothing.\n- `stdlib:` hand-rolled code stdlib already covers. Name API.\n- `native:` dependency\u002Fcustom code platform\u002Fframework\u002FDB\u002Fbrowser\u002FOS already covers. Name feature.\n- `yagni:` abstraction\u002Fconfig\u002Flayer with one impl, no real caller, or unproven need.\n- `shrink:` same behavior with fewer concepts\u002Flines. Show shorter replacement when concise.\n\n## Rules\n\n- Analysis only; no code edits.\n- Prefer high-leverage findings over exhaustive nitpicks.\n- Favor deletion\u002Fsimplification over new abstraction.\n- Prefer stdlib, native features, and existing deps over custom code\u002Fnew deps.\n- For over-engineering, name what to cut and what replaces it; include `net: -N lines possible` when meaningful and cheap.\n- Correctness, tests, docs, deps, and perf gaps still count even when line count grows or does not shrink.\n- Do not chase tiny line cuts that obscure behavior or fight repo conventions.\n- Validate against existing patterns\u002Flocal rules.\n- Separate quick wins from strategic refactors.\n- Report uncertainty when confidence low.\n- Do not force optimization when asymptotic win\u002Ftrade-off is poor.\n- If nothing useful to cut in simplify-only pass, say lean already.\n\n## Output\n\n```markdown\n# Codebase Improvement Summary\n\n## Executive Summary\n- 2-4 sentences: health + biggest opportunities\n\n## Top Improvements To Make Now\n- [Impact | Effort | Confidence] Title\n  - Files\u002FSymbols:\n  - Evidence:\n  - Smallest viable change:\n  - Why now:\n\n## Quick Wins\n- Low-risk, high-leverage cleanups\n\n## Strategic Refactors\n- Larger changes needing planning\n\n## Deletion \u002F De-scope Opportunities\n- Code, configs, abstractions, or deps likely removable\n\n## Test \u002F Docs \u002F Dependency Gaps\n- Missing coverage, stale docs, missing API docs, toolchain cleanup\n\n## Questions \u002F Assumptions\n- Uncertainties needing confirmation\n```\n",{"name":5,"description":7},"main","e24b64bdac040ad169ed16b14853eff1b20cd726","skills_archive\u002Fanalyze-codebase-improvements",0,"https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates","https:\u002F\u002Fgithub.com\u002FBumpyClock","2026-11-14 03:12:06",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add BumpyClock\u002Fagent-templates --skill analyze-codebase-improvements",{"tool":37,"command":38},"bunx","bunx skills add BumpyClock\u002Fagent-templates --skill analyze-codebase-improvements",{"tool":40,"command":41},"pnpm","pnpm dlx skills add BumpyClock\u002Fagent-templates --skill analyze-codebase-improvements","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fanalyze-codebase-improvements\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",390,"https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fanalyze-codebase-improvements\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M79FEE6E257MWVEBY43X0NVN","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79FEB8GTJC6ZHDK67T40R20","workflow-from-chats","Extract preferences from agent chats → skills, rules, workflow docs. For learning preferences, mining feedback, personalizing workflows.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fworkflow-from-chats\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79FE7TMNGVZZ0M8NV4N0X6N","winui3-csharp-app","WinUI 3 \u002F Windows App SDK desktop apps in C#\u002FXAML. MVVM, bindings, navigation, Mica\u002FAcrylic, windowing, packaging, performance.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwinui3-csharp-app\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79FE31HY46BHN67CQGB7MVJ","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79FE0N7MGWDG8SCD60FWTV5","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise status update.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79FDYBJG9QNCQC0MMVBDT80","weekly-review","Produce a short weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fweekly-review\u002FSKILL.md",[],[]]