[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E3ZNF4MB70MJN6EXV48BWS":3,"skill-same:01M6E3ZNF4MB70MJN6EXV48BWS":71},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6E3ZNF4MB70MJN6EXV48BWS","code-simplifier",null,"simplifies and refines code for clarity, consistency, and maintainability while preserving exact functionality. use when chatgpt needs to review, clean up, or simplify recently modified code, align code with project conventions, reduce unnecessary complexity, improve readability, or make implementation details more explicit without changing behavior.","1024XEngineer\u002Fbytemind","1024XEngineer","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F268547415?v=4","01M6E269SXV33P2PN20YB4GKXS","XEngineer Camp","01M6E3ZBC2YEQVSRCAZK449022",27,"MIT","https:\u002F\u002Fgithub.com\u002F1024XEngineer\u002Fbytemind\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcode-simplifier\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"code","code simplifier","use","maintainability","readability","project","conventions","align","clean","implementation","complexity","up","review","behavior","clarity","improve","simplify","chatgpt","project conventions","2026-11-10 10:12:30",false,"---\nname: code-simplifier\ndescription: simplifies and refines code for clarity, consistency, and maintainability while preserving exact functionality. use when chatgpt needs to review, clean up, or simplify recently modified code, align code with project conventions, reduce unnecessary complexity, improve readability, or make implementation details more explicit without changing behavior.\n---\n\nRefine recently modified code for clarity, consistency, and maintainability while preserving exact functionality.\n\n## Core behavior\n\nPreserve behavior exactly.\n\n- Do not change features, outputs, side effects, or observable behavior.\n- Change how the code is written, not what it does.\n- Do not broaden scope unless the user explicitly asks for a wider review.\n\nFocus on code that was recently modified or touched in the current session.\n\n- Prefer refining the code that was just written or edited.\n- Avoid unrelated cleanup in untouched areas.\n\nPrefer explicit, readable code over compact code.\n\n- Choose clarity over brevity.\n- Avoid clever one-liners when a straightforward structure is easier to read.\n- Avoid nested ternary operators. Use `if\u002Felse` chains or `switch` statements for multiple conditions.\n\n## Apply project conventions\n\nWhen the repository or provided guidance includes project standards such as `CLAUDE.md`, follow them closely.\n\nCommon conventions to apply when present:\n\n- Use ES modules with proper import sorting and explicit extensions where required.\n- Prefer the `function` keyword over arrow functions when that is the project standard.\n- Add explicit return type annotations for top-level functions when the project expects them.\n- Follow established React component patterns with explicit `Props` types.\n- Use the repository’s preferred error-handling patterns and avoid introducing unnecessary `try\u002Fcatch`.\n- Preserve existing naming conventions unless renaming clearly improves consistency and does not increase scope.\n\nIf no project standard is available, preserve the local style of the surrounding code while still simplifying it.\n\n## What to improve\n\nLook for opportunities to:\n\n- reduce unnecessary nesting\n- remove redundant abstractions\n- eliminate duplicated logic when the result is clearer\n- consolidate closely related logic\n- improve variable, function, and component names when that materially improves readability\n- remove comments that only restate obvious code behavior\n- make control flow easier to follow\n- keep helpful abstractions that improve organization\n\nDo not simplify in ways that:\n\n- reduce clarity\n- make debugging harder\n- combine too many concerns into one function or component\n- replace readable code with dense shorthand\n- remove abstractions that help structure the codebase\n\n## Review process\n\nUse this workflow:\n\n1. Identify the code that was recently modified.\n2. Check for project-specific conventions from repository guidance and nearby code.\n3. Find the highest-value simplifications that preserve behavior.\n4. Apply small, clear refinements.\n5. Re-check that functionality remains unchanged.\n6. Report only meaningful changes that affect readability, structure, or maintainability.\n\n## Output expectations\n\nWhen making changes:\n\n- keep edits scoped and intentional\n- preserve public interfaces unless the same interface can be expressed more clearly without behavioral change\n- avoid noisy reformatting unrelated to the simplification\n- prefer a few high-confidence improvements over broad cosmetic churn\n\nWhen summarizing your work:\n\n- briefly explain the significant simplifications\n- mention any project conventions you applied\n- note any areas you intentionally left unchanged to avoid altering behavior\n","Refine recently modified code for clarity, consistency, and maintainability while preserving exact functionality.\n\n## Core behavior\n\nPreserve behavior exactly.\n\n- Do not change features, outputs, side effects, or observable behavior.\n- Change how the code is written, not what it does.\n- Do not broaden scope unless the user explicitly asks for a wider review.\n\nFocus on code that was recently modified or touched in the current session.\n\n- Prefer refining the code that was just written or edited.\n- Avoid unrelated cleanup in untouched areas.\n\nPrefer explicit, readable code over compact code.\n\n- Choose clarity over brevity.\n- Avoid clever one-liners when a straightforward structure is easier to read.\n- Avoid nested ternary operators. Use `if\u002Felse` chains or `switch` statements for multiple conditions.\n\n## Apply project conventions\n\nWhen the repository or provided guidance includes project standards such as `CLAUDE.md`, follow them closely.\n\nCommon conventions to apply when present:\n\n- Use ES modules with proper import sorting and explicit extensions where required.\n- Prefer the `function` keyword over arrow functions when that is the project standard.\n- Add explicit return type annotations for top-level functions when the project expects them.\n- Follow established React component patterns with explicit `Props` types.\n- Use the repository’s preferred error-handling patterns and avoid introducing unnecessary `try\u002Fcatch`.\n- Preserve existing naming conventions unless renaming clearly improves consistency and does not increase scope.\n\nIf no project standard is available, preserve the local style of the surrounding code while still simplifying it.\n\n## What to improve\n\nLook for opportunities to:\n\n- reduce unnecessary nesting\n- remove redundant abstractions\n- eliminate duplicated logic when the result is clearer\n- consolidate closely related logic\n- improve variable, function, and component names when that materially improves readability\n- remove comments that only restate obvious code behavior\n- make control flow easier to follow\n- keep helpful abstractions that improve organization\n\nDo not simplify in ways that:\n\n- reduce clarity\n- make debugging harder\n- combine too many concerns into one function or component\n- replace readable code with dense shorthand\n- remove abstractions that help structure the codebase\n\n## Review process\n\nUse this workflow:\n\n1. Identify the code that was recently modified.\n2. Check for project-specific conventions from repository guidance and nearby code.\n3. Find the highest-value simplifications that preserve behavior.\n4. Apply small, clear refinements.\n5. Re-check that functionality remains unchanged.\n6. Report only meaningful changes that affect readability, structure, or maintainability.\n\n## Output expectations\n\nWhen making changes:\n\n- keep edits scoped and intentional\n- preserve public interfaces unless the same interface can be expressed more clearly without behavioral change\n- avoid noisy reformatting unrelated to the simplification\n- prefer a few high-confidence improvements over broad cosmetic churn\n\nWhen summarizing your work:\n\n- briefly explain the significant simplifications\n- mention any project conventions you applied\n- note any areas you intentionally left unchanged to avoid altering behavior\n",{"name":5,"description":7},"main","f259496ed7f959b3400c57e2d3d4d0a548d4b6a3",".agents\u002Fskills\u002Fcode-simplifier",6,"https:\u002F\u002Fgithub.com\u002F1024XEngineer\u002Fbytemind","https:\u002F\u002F1024xengineer.github.io\u002Fbytemind\u002F","https:\u002F\u002Fgithub.com\u002F1024XEngineer","An open, hands-on platform where engineers grow through real projects, open-source collaboration, and architectural thinking.","2026-07-29 12:33:51",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add 1024XEngineer\u002Fbytemind --skill code-simplifier",{"tool":63,"command":64},"bunx","bunx skills add 1024XEngineer\u002Fbytemind --skill code-simplifier",{"tool":66,"command":67},"pnpm","pnpm dlx skills add 1024XEngineer\u002Fbytemind --skill code-simplifier","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F1024XEngineer\u002Fbytemind\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcode-simplifier\u002FSKILL.md",true,[],[72,94,123,141,168,182],{"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":43},"01M6E40DD4NH8R8JYQEVN4RVQJ","write-rfc","Produce reviewable technical proposals with explicit decision rationale and rollout.","https:\u002F\u002Fgithub.com\u002F1024XEngineer\u002Fbytemind\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fwrite-rfc\u002FSKILL.md",[],[79,80,81,82,83,84,85,86,87,88,89,90,91,92,93],"write","RFC","write rfc","planning","technical design","options","migration","rollout","proposals","user","technical","decision","produce","architecture","design",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":108,"publishedAt":43},"01M6E407WDFPFMZ3NFNPBVC0GJ","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002F1024XEngineer\u002Fbytemind\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fskill-creator\u002FSKILL.md",[100,105],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":106,"categoryName":107,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000023","Skill与智能体开发",[109,110,111,112,113,114,115,116,117,118,119,120,121,26,122,39],"skill creator","create","benchmark","run","variance analysis","test","run evals","performance","analysis","users","existing skill","optimize","evals","edit",{"skillNo":124,"name":36,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":132,"publishedAt":43},"01M6E40415NE0DJB3WS0QK68M6","Review current code changes with focus on correctness, regressions, and missing tests.","https:\u002F\u002Fgithub.com\u002F1024XEngineer\u002Fbytemind\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Freview\u002FSKILL.md",[128,131],{"categoryNo":129,"categoryName":130,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[36,133,134,135,136,88,137,24,138,139,140],"risk assessment","missing","tests","focus","risk","assessment","code review","merge",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":43},"01M6E400ME5ZDK25R08AR3Q2TA","repo-onboarding","Build repository context quickly: structure, entrypoints, build chain, and core modules.","https:\u002F\u002Fgithub.com\u002F1024XEngineer\u002Fbytemind\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Frepo-onboarding\u002FSKILL.md",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000038","人力资源",[151,152,153,154,155,156,157,158,159,33,160,161,162,163,164,165,166,167],"repo","onboarding","repo onboarding","context setup","team","chain","time","structure","build","modules","context","first","repository","core","setup","team handoff","handoff",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":43},"01M6E3ZXZJTNBZ22Q0S1M9D5JD","github-pr","Analyze pull request context and highlight merge risks from diffs and comments.","https:\u002F\u002Fgithub.com\u002F1024XEngineer\u002Fbytemind\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fgithub-pr\u002FSKILL.md",[],[175,176,177,117,137,178,138,179,133,140,180,36,181,88,161],"pr","github","github pr","pull","pull request","diffs","analyze",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":43},"01M6E3ZVAAQ2GVJH46BPC75C9R","bug-investigation","Diagnose issues with reproducible evidence before proposing a fix.","https:\u002F\u002Fgithub.com\u002F1024XEngineer\u002Fbytemind\u002Fblob\u002Fmain\u002Finternal\u002Fskills\u002Fbug-investigation\u002FSKILL.md",[],[189,190,191,192,193,194,195,196,88,197,198,199,200,114],"Bug Investigation","bug","investigation","production incident","incident","reports","evidence","fix","Production","Reproducible","issues","diagnose"]