[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SFTE028MYY4HJPRWC9RJG":3,"skill-same:01M71SFTE028MYY4HJPRWC9RJG":46},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M71SFTE028MYY4HJPRWC9RJG","maintaining-codebase",null,"Praneeth-Suresh\u002FBeryl","Praneeth-Suresh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F86470588?v=4","01M71SF2BCZ4JMKKYZR66WNHAF","Praneeth Suresh","01M71SF2C5JMS7B9676HSA2SG6",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fmaintaining-codebase\u002FSKILL.md",[],[18,19],"codebase","maintaining codebase","2026-11-10 13:02:02",false,"# Maintaining Codebase\n\n## Purpose\n\nTurn one request for sustained codebase maintenance into an evidence-led,\nrepository-wide improvement program. It reduces technical debt without treating\n\"improve everything\" as permission for a risky, unreviewed rewrite.\n\n## Trigger\n\nUse for periodic maintenance, technical-debt reduction, code-quality\nimprovement, complexity management, or a whole-repository upkeep request.\nThis skill owns the top-level maintenance assessment and prioritisation.\n\n## Assessment\n\n1. Read the repository's architecture, ubiquitous language, testing policy,\n   design decisions, ownership rules, and current change state.\n2. Gather evidence rather than rating files by intuition: churn and hotspot\n   data, dependency state, lint\u002Ftype\u002Ftest\u002Fbuild output when configured,\n   boundary\u002Fimport patterns, duplication, complexity indicators, stale docs,\n   dead generated assets, security advisories, and recent incident or failure\n   evidence. State unavailable evidence and do not invent it.\n3. For each finding, name the owning bounded context, evidence, user impact,\n   likely root cause, risk level, and the smallest protecting test or check.\n4. Score and rank work using impact, likelihood, change cost, and confidence.\n   Separate quick safe cleanup from architectural debt, product work, and\n   unproven speculation.\n\n## Maintenance program\n\nProduce a compact reviewable program containing:\n\n- a repository health snapshot and an explicit list of evidence gaps;\n- a prioritised backlog with risk, ownership, expected benefit, and rollback\n  boundary;\n- dependency-ordered, behavior-preserving extraction\u002Frefactor slices;\n- a cadence for repeating the assessment and measurable exit signals;\n- test, documentation, security, performance, accessibility, and observability\n  follow-ups where evidence supports them.\n\nDo not modify code during the assessment. Present the program and wait for\napproval before any implementation. After approval, route each behavior change\nthrough the normal `planning` or `systematic-debugging` workflow, and hand\neach behavior-preserving refactor slice to `simplifying-code`. Use\n`.\u002F.beryl\u002Fagent\u002Fscripts\u002Fentropy-hotspots.sh` for churn and hotspot evidence.\nNever bundle unrelated cleanup, weaken tests, claim all debt is removed, or\nconvert a finding into a feature without separate product approval.\n\n## Output\n\nUse this structure:\n\n```yaml\nskill: maintaining-codebase\nstatus: success\nhealth_snapshot: \"\u003Cevidence-based summary>\"\nevidence_gaps: [\"\u003Cunavailable input>\"]\npriorities:\n  - finding: \"\u003Cproblem>\"\n    bounded_context: \"\u003Cowner>\"\n    evidence: \"\u003Cfacts>\"\n    risk: \"\u003Clow|medium|high>\"\n    protecting_check: \"\u003Ccommand or test>\"\nmaintenance_slices: [\"\u003Cdependency-ordered, reviewable change>\"]\ncadence: \"\u003Crepeat interval and trigger>\"\napproval_required_before_implementation: true\n```\n",{},"main","3a5bd7e327cbdad81a70b624ec3fc6e43ec91f12",".beryl\u002Fagent\u002Fskills\u002Fmaintaining-codebase",0,"https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh","Just built it.","2026-11-09 18:59:34",{"source":7,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Praneeth-Suresh\u002FBeryl --skill maintaining-codebase",{"tool":38,"command":39},"bunx","bunx skills add Praneeth-Suresh\u002FBeryl --skill maintaining-codebase",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Praneeth-Suresh\u002FBeryl --skill maintaining-codebase","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fmaintaining-codebase\u002FSKILL.md",true,[],[47,72,79,111,136,151],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":51,"licenseFileUrl":52,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":20},"01M71SGEFHAT82F5TQH73XY6H8","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","MIT","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fverification-before-completion\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71],"verification","verification before completion","committing","commands","about","work","claims","output","evidence","when","assertions","use","claim","prs","complete","running",{"skillNo":73,"name":74,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":20},"01M71SGD1DV15B9Z2S5V3M8YPH","using-beryl","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fusing-beryl\u002FSKILL.md",[],[78],"using beryl",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":93,"publishedAt":20},"01M71SGAJ7D211GQR4703TTZCW","understand-codebase","Teach a developer how a repository, subsystem, execution path, migration, diff, commit, branch, or pull request works. Use when the user asks to understand, explain, map, walk through, explore, or quiz themselves on code, or asks for an interactive HTML understanding artifact.","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Funderstand-codebase\u002FSKILL.md",[85,90],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":91,"categoryName":92,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000039","教师与教育",[94,18,95,96,97,98,99,100,101,102,67,65,103,104,105,106,107,108,109,110],"understand","understand codebase","branch","diff","for","explore","execution","quiz","map","code","commit","interactive","explain","artifact","how","pull request","pull",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":51,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":126,"publishedAt":20},"01M71SG8H7CZGRND4C2BS49RV2","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Ftest-driven-development\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[118,123],{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":124,"categoryName":125,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000018","写作与文案",[127,128,129,130,131,132,133,67,65,103,134,135],"driven","test","test driven development","development","feature","implementing","writing","bugfix","implementation",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":51,"licenseFileUrl":140,"sourceHtmlUrl":141,"categories":142,"keywords":144,"publishedAt":20},"01M71SG4N855A3ASYXWFX45DH5","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fsystematic-debugging\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[143],{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},[145,146,147,148,67,65,128,149,150],"systematic","debugging","systematic debugging","fixes","behavior","bug",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":20},"01M71SG18JMNV8ED6XQ97Z48X0","simplifying-code","Use when code in a specific module or area is hard to understand or change, when the user asks to simplify, refactor, clean up, or improve the design or architecture of some code, or when a maintenance program hands over a refactor slice. Finds unmanaged complexity from evidence and removes it with small, behavior-preserving changes.","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fsimplifying-code\u002FSKILL.md",[157],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[159,103,160,161,162,163,164,165,65,67,166,167,168,169,170,171,64,172,173,174],"simplifying code","design","change","with","architecture","program","simplify","module","changes","improve","clean","up","slice","complexity","behavior-preserving","maintenance"]