[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HZ6C1WBC0AWGSWTFB68GAF":3,"skill-same:01M6HZ6C1WBC0AWGSWTFB68GAF":97},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6HZ6C1WBC0AWGSWTFB68GAF","repo-onboarding",null,"repository discovery, entrypoint mapping, and fast onboarding for unfamiliar codebases. use when the repo is new, mixed, legacy, monorepo-shaped, poorly documented, or when the next safe step is blocked on understanding layout, ownership, and commands.","ldilov\u002Fharness-forge","ldilov","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25016670?v=4","01M6HYXAEJP0KYT2DF86WYN8QK","Lazar Dilov","01M6HYXAJETHAW5DD5TAAFEQ7D",6,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Frepo-onboarding\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"onboarding","repo onboarding","repo","for","safe","entrypoint","ownership","mapping","layout","commands","next","Legacy","use","monorepo","discovery","repository","fast","2026-11-10 10:12:30",false,"---\nname: repo-onboarding\ndescription: repository discovery, entrypoint mapping, and fast onboarding for unfamiliar codebases. use when the repo is new, mixed, legacy, monorepo-shaped, poorly documented, or when the next safe step is blocked on understanding layout, ownership, and commands.\n---\n\n# Repository Onboarding\n\n## Trigger Signals\n\n- the repository is unfamiliar, mixed, legacy, or monorepo-shaped\n- the next safe step is blocked on understanding layout, ownership, or workflow\n- docs are sparse, stale, or scattered across many entrypoints\n\n## Inspect First\n\n- repo root files such as `README.md`, top-level manifests, CI config, container config, and deployment hints\n- `AGENTS.md`, `.agents\u002Fskills\u002F`, `.specify\u002F`, or other repo-native guidance surfaces when present\n- top-level source, app, package, service, infra, and test directories\n- `CODEOWNERS`, contribution docs, issue or PR templates, and other health signals when present\n\n## Workflow\n\n1. identify the repo archetype and dominant implementation surfaces\n2. map build, test, run, deploy, and validation entrypoints\n3. infer ownership, boundaries, and high-risk hotspots from structure and metadata\n4. call out drift, missing validation, generated code, or conflicting conventions\n5. recommend the next best action and the best repo surfaces to load before changing code\n\n## Output Contract\n\n- repository summary with dominant languages, runtimes, and repo shape\n- key commands and entrypoints for build, test, run, and release\n- hotspots, blockers, and missing information that affect safe changes\n- recommended next action with the specific files or dirs to inspect next\n\n## Failure Modes\n\n- repo layout is too large to inspect safely in one pass\n- generated or vendored code hides the real ownership boundaries\n- no reliable build or validation entrypoints can be found\n\n## Escalation\n\n- escalate when ownership or architecture cannot be inferred safely\n- escalate when there is no trustworthy validation path for a risky change\n- escalate when docs and code disagree about the active workflow\n\n## References\n\n- `skills\u002Frepo-onboarding\u002Freferences\u002Foutput-template.md`\n- `skills\u002Frepo-onboarding\u002Freferences\u002Fdiscovery-checklist.md`\n- `skills\u002Frepo-onboarding\u002Freferences\u002Frepo-archetypes.md`\n- `skills\u002Frepo-onboarding\u002Freferences\u002Fownership-and-health-signals.md`\n- `skills\u002Frepo-onboarding\u002Freferences\u002Fcommand-discovery.md`\n- `skills\u002Frepo-onboarding\u002Freferences\u002Fmonorepo-signals.md`\n- `skills\u002Frepo-onboarding\u002Freferences\u002Fexamples.md`\n","# Repository Onboarding\n\n## Trigger Signals\n\n- the repository is unfamiliar, mixed, legacy, or monorepo-shaped\n- the next safe step is blocked on understanding layout, ownership, or workflow\n- docs are sparse, stale, or scattered across many entrypoints\n\n## Inspect First\n\n- repo root files such as `README.md`, top-level manifests, CI config, container config, and deployment hints\n- `AGENTS.md`, `.agents\u002Fskills\u002F`, `.specify\u002F`, or other repo-native guidance surfaces when present\n- top-level source, app, package, service, infra, and test directories\n- `CODEOWNERS`, contribution docs, issue or PR templates, and other health signals when present\n\n## Workflow\n\n1. identify the repo archetype and dominant implementation surfaces\n2. map build, test, run, deploy, and validation entrypoints\n3. infer ownership, boundaries, and high-risk hotspots from structure and metadata\n4. call out drift, missing validation, generated code, or conflicting conventions\n5. recommend the next best action and the best repo surfaces to load before changing code\n\n## Output Contract\n\n- repository summary with dominant languages, runtimes, and repo shape\n- key commands and entrypoints for build, test, run, and release\n- hotspots, blockers, and missing information that affect safe changes\n- recommended next action with the specific files or dirs to inspect next\n\n## Failure Modes\n\n- repo layout is too large to inspect safely in one pass\n- generated or vendored code hides the real ownership boundaries\n- no reliable build or validation entrypoints can be found\n\n## Escalation\n\n- escalate when ownership or architecture cannot be inferred safely\n- escalate when there is no trustworthy validation path for a risky change\n- escalate when docs and code disagree about the active workflow\n\n## References\n\n- `skills\u002Frepo-onboarding\u002Freferences\u002Foutput-template.md`\n- `skills\u002Frepo-onboarding\u002Freferences\u002Fdiscovery-checklist.md`\n- `skills\u002Frepo-onboarding\u002Freferences\u002Frepo-archetypes.md`\n- `skills\u002Frepo-onboarding\u002Freferences\u002Fownership-and-health-signals.md`\n- `skills\u002Frepo-onboarding\u002Freferences\u002Fcommand-discovery.md`\n- `skills\u002Frepo-onboarding\u002Freferences\u002Fmonorepo-signals.md`\n- `skills\u002Frepo-onboarding\u002Freferences\u002Fexamples.md`\n",{"name":5,"description":7},"main","27337828f396bcf279d7c4353a4a4f0cdc97659f","skills\u002Frepo-onboarding",1,"https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge","https:\u002F\u002Fgithub.com\u002Fldilov","2026-05-19 21:48:38",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add ldilov\u002Fharness-forge --skill repo-onboarding",{"tool":59,"command":60},"bunx","bunx skills add ldilov\u002Fharness-forge --skill repo-onboarding",{"tool":62,"command":63},"pnpm","pnpm dlx skills add ldilov\u002Fharness-forge --skill repo-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Frepo-onboarding\u002FSKILL.md",true,[67,73,77,81,85,89,93],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fcommand-discovery.md","REFERENCE","参考文档",500,"https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Frepo-onboarding\u002Freferences\u002Fcommand-discovery.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fdiscovery-checklist.md",565,"https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Frepo-onboarding\u002Freferences\u002Fdiscovery-checklist.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fexamples.md",504,"https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Frepo-onboarding\u002Freferences\u002Fexamples.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fmonorepo-signals.md",491,"https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Frepo-onboarding\u002Freferences\u002Fmonorepo-signals.md",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Foutput-template.md",455,"https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Frepo-onboarding\u002Freferences\u002Foutput-template.md",{"path":90,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fownership-and-health-signals.md",614,"https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Frepo-onboarding\u002Freferences\u002Fownership-and-health-signals.md",{"path":94,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Frepo-archetypes.md",425,"https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Frepo-onboarding\u002Freferences\u002Frepo-archetypes.md",[98,127,157,176,199,211],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":109,"publishedAt":41},"01M6HZ7WE4DSYWPX0W2JX9BD8K","typescript-engineering","typescript and javascript engineering guidance seeded from the harness forge knowledge base. use when the repo or task is dominated by .ts, .tsx, package.json, tsconfig, node.js services, react, next.js, frontend tooling, or multi-package workspaces where type boundaries matter.","https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Ftypescript-engineering\u002FSKILL.md",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[110,111,112,113,114,115,116,117,118,119,120,121,26,36,122,123,124,34,125,126],"typescript","engineering","typescript engineering","frontend","javascript","react","harness","package","forge","Next.js","knowledge","node","workspaces","tsx","task","knowledge base","type",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":139,"publishedAt":41},"01M6HZ7QRWHQP72E7DPB6W5S6C","token-budget-optimizer","compact context, reuse existing runtime artifacts, and choose the smallest authoritative surface before expanding prompt history. use when the task is growing large, when earlier repo intelligence already exists, or when repeated rescans would waste tokens without adding new evidence.","https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Ftoken-budget-optimizer\u002FSKILL.md",[133,136],{"categoryNo":134,"categoryName":135,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":137,"categoryName":138,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000040","财务",[140,141,142,143,144,145,146,147,26,148,149,36,150,124,151,152,153,154,155,156],"Budget","optimizer","token","token budget","token budget optimizer","artifacts","choose","history","prompt","context","evidence","intelligence","compact","tokens","runtime","reuse","Existing",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":166,"publishedAt":41},"01M6HZ7MMX3ZZP4KF2FVC2EHP0","test-strategy-and-coverage","Define right-sized test layers and coverage priorities for a change.","https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Ftest-strategy-and-coverage\u002FSKILL.md",[163],{"categoryNo":164,"categoryName":165,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000008","测试与质量",[167,168,169,170,171,172,173,174,175,27],"test","strategy","coverage","test strategy","test strategy and coverage","change","priorities","define","layers",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":41},"01M6HZ7HE9C6MGWT9JG17Z3Y3M","speckit-taskstoissues","Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.","https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-taskstoissues\u002FSKILL.md",[],[183,184,185,186,187,188,189,145,190,191,192,193,194,195,33,196,197,198,27,156],"speckit taskstoissues","speckit","design","directory","project structure","tasks","github issues","issues","specify","convert","dependency","structure","project","feature","actionable","kit",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":205,"publishedAt":41},"01M6HZ7E2NMYB9N2GKYVRF09AK","speckit-tasks","Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.","https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-tasks\u002FSKILL.md",[],[188,206,184,185,186,207,187,208,145,191,193,194,195,33,196,197,209,210,198,27],"speckit tasks","github","generate","spec-kit","with",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":217,"publishedAt":41},"01M6HZ7AS0E880YSZN4FEFF6QF","speckit-specify","Create or update the feature specification from a natural language feature description.","https:\u002F\u002Fgithub.com\u002Fldilov\u002Fharness-forge\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-specify\u002FSKILL.md",[],[191,218,184,186,219,207,187,220,221,222,223,224,194,195,33,196,209,210,225,198],"speckit specify","spec","create","update","templates","specification","natural language","feature specification"]