[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FPMQSGE7XD79MZBV2GN0G":3,"skill-same:01M70FPMQSGE7XD79MZBV2GN0G":78},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M70FPMQSGE7XD79MZBV2GN0G","code-tour",null,"Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured \"explain how this works\" requests. Use when the user asks for a code tour, onboarding walkthrough, PR tour, or an explanation of how a subsystem works.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcode-tour\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"code","tour","code tour","requests","with","explain","file","use","for","pr","rca","line","how","create","architecture","when","persona","files","pr tour","walkthrough","2026-11-10 10:12:30",false,"---\nname: code-tour\ndescription: Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured \"explain how this works\" requests. Use when the user asks for a code tour, onboarding walkthrough, PR tour, or an explanation of how a subsystem works.\nmetadata:\n  origin: ECC\n---\n\n# Code Tour\n\nCreate **CodeTour** `.tour` files for codebase walkthroughs that open directly to real files and line ranges. Tours live in `.tours\u002F` and are meant for the CodeTour format, not ad hoc Markdown notes.\n\nA good tour is a narrative for a specific reader:\n- what they are looking at\n- why it matters\n- what path they should follow next\n\nOnly create `.tour` JSON files. Do not modify source code as part of this skill.\n\n## When to Use\n\nUse this skill when:\n- the user asks for a code tour, onboarding tour, architecture walkthrough, or PR tour\n- the user says \"explain how X works\" and wants a reusable guided artifact\n- the user wants a ramp-up path for a new engineer or reviewer\n- the task is better served by a guided sequence than a flat summary\n\nExamples:\n- onboarding a new maintainer\n- architecture tour for one service or package\n- PR-review walk-through anchored to changed files\n- RCA tour showing the failure path\n- security review tour of trust boundaries and key checks\n\n## When NOT to Use\n\n| Instead of code-tour | Use |\n| --- | --- |\n| A one-off explanation in chat is enough | answer directly |\n| The user wants prose docs, not a `.tour` artifact | `documentation-lookup` or repo docs editing |\n| The task is implementation or refactoring | do the implementation work |\n| The task is broad codebase onboarding without a tour artifact | `codebase-onboarding` |\n\n## Workflow\n\n### 1. Discover\n\nExplore the repo before writing anything:\n- README and package\u002Fapp entry points\n- folder structure\n- relevant config files\n- the changed files if the tour is PR-focused\n\nDo not start writing steps before you understand the shape of the code.\n\n### 2. Infer the reader\n\nDecide the persona and depth from the request.\n\n| Request shape | Persona | Suggested depth |\n| --- | --- | --- |\n| \"onboarding\", \"new joiner\" | `new-joiner` | 9-13 steps |\n| \"quick tour\", \"vibe check\" | `vibecoder` | 5-8 steps |\n| \"architecture\" | `architect` | 14-18 steps |\n| \"tour this PR\" | `pr-reviewer` | 7-11 steps |\n| \"why did this break\" | `rca-investigator` | 7-11 steps |\n| \"security review\" | `security-reviewer` | 7-11 steps |\n| \"explain how this feature works\" | `feature-explainer` | 7-11 steps |\n| \"debug this path\" | `bug-fixer` | 7-11 steps |\n\n### 3. Read and verify anchors\n\nEvery file path and line anchor must be real:\n- confirm the file exists\n- confirm the line numbers are in range\n- if using a selection, verify the exact block\n- if the file is volatile, prefer a pattern-based anchor\n\nNever guess line numbers.\n\n### 4. Write the `.tour`\n\nWrite to:\n\n```text\n.tours\u002F\u003Cpersona>-\u003Cfocus>.tour\n```\n\nKeep the path deterministic and readable.\n\n### 5. Validate\n\nBefore finishing:\n- every referenced path exists\n- every line or selection is valid\n- the first step is anchored to a real file or directory\n- the `ref` points at a branch or commit that actually has every file the tour references (see below)\n- the tour tells a coherent story rather than listing files\n\n## The `ref` Field\n\n`ref` ties the tour to a git branch or commit. It matters more than it looks: when `ref` is not the branch the reader has checked out, CodeTour opens each step's file from that revision in git, not from the files on disk. If a file is not in that revision, the step will not open — the reader sees *\"The editor could not be opened because the file was not found\"* even though the file is sitting right there. The tour and its comments still show, so the real cause is easy to miss.\n\nPick `ref` by tour type:\n\n| Tour type | Set `ref` to |\n| --- | --- |\n| PR tour | the PR branch — never the base branch |\n| Onboarding \u002F architecture | the branch the reader will be on (often `main`), or leave it out |\n| Not sure | leave `ref` out, so CodeTour reads files straight from disk |\n\nThe PR case is the common trap: a PR usually adds new files, and new files do not exist on the base branch yet. Point `ref` at the base (e.g. `develop`) and every step on a new file fails to open.\n\nBefore finishing, confirm each step's file actually exists at the `ref` you chose.\n\n## Step Types\n\n### Content\n\nUse sparingly, usually only for a closing step:\n\n```json\n{ \"title\": \"Next Steps\", \"description\": \"You can now trace the request path end to end.\" }\n```\n\nDo not make the first step content-only.\n\n### Directory\n\nUse to orient the reader to a module:\n\n```json\n{ \"directory\": \"src\u002Fservices\", \"title\": \"Service Layer\", \"description\": \"The core orchestration logic lives here.\" }\n```\n\n### File + line\n\nThis is the default step type:\n\n```json\n{ \"file\": \"src\u002Fauth\u002Fmiddleware.ts\", \"line\": 42, \"title\": \"Auth Gate\", \"description\": \"Every protected request passes here first.\" }\n```\n\n### Selection\n\nUse when one code block matters more than the whole file:\n\n```json\n{\n  \"file\": \"src\u002Fcore\u002Fpipeline.ts\",\n  \"selection\": {\n    \"start\": { \"line\": 15, \"character\": 0 },\n    \"end\": { \"line\": 34, \"character\": 0 }\n  },\n  \"title\": \"Request Pipeline\",\n  \"description\": \"This block wires validation, auth, and downstream execution.\"\n}\n```\n\n### Pattern\n\nUse when exact lines may drift:\n\n```json\n{ \"file\": \"src\u002Fapp.ts\", \"pattern\": \"export default class App\", \"title\": \"Application Entry\" }\n```\n\n### URI\n\nUse for PRs, issues, or docs when helpful:\n\n```json\n{ \"uri\": \"https:\u002F\u002Fgithub.com\u002Forg\u002Frepo\u002Fpull\u002F456\", \"title\": \"The PR\" }\n```\n\n## Writing Rule: SMIG\n\nEach description should answer:\n- **Situation**: what the reader is looking at\n- **Mechanism**: how it works\n- **Implication**: why it matters for this persona\n- **Gotcha**: what a smart reader might miss\n\nKeep descriptions compact, specific, and grounded in the actual code.\n\n## Narrative Shape\n\nUse this arc unless the task clearly needs something different:\n1. orientation\n2. module map\n3. core execution path\n4. edge case or gotcha\n5. closing \u002F next move\n\nThe tour should feel like a path, not an inventory.\n\n## Example\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Faka.ms\u002Fcodetour-schema\",\n  \"title\": \"API Service Tour\",\n  \"description\": \"Walkthrough of the request path for the payments service.\",\n  \"ref\": \"main\",\n  \"steps\": [\n    {\n      \"directory\": \"src\",\n      \"title\": \"Source Root\",\n      \"description\": \"All runtime code for the service starts here.\"\n    },\n    {\n      \"file\": \"src\u002Fserver.ts\",\n      \"line\": 12,\n      \"title\": \"Entry Point\",\n      \"description\": \"The server boots here and wires middleware before any route is reached.\"\n    },\n    {\n      \"file\": \"src\u002Froutes\u002Fpayments.ts\",\n      \"line\": 8,\n      \"title\": \"Payment Routes\",\n      \"description\": \"Every payments request enters through this router before hitting service logic.\"\n    },\n    {\n      \"title\": \"Next Steps\",\n      \"description\": \"You can now follow any payment request end to end with the main anchors in place.\"\n    }\n  ]\n}\n```\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n| --- | --- |\n| Flat file listing | Tell a story with dependency between steps |\n| Generic descriptions | Name the concrete code path or pattern |\n| Guessed anchors | Verify every file and line first |\n| Too many steps for a quick tour | Cut aggressively |\n| First step is content-only | Anchor the first step to a real file or directory |\n| Persona mismatch | Write for the actual reader, not a generic engineer |\n\n## Best Practices\n\n- keep step count proportional to repo size and persona depth\n- use directory steps for orientation, file steps for substance\n- for PR tours, cover changed files first\n- for monorepos, scope to the relevant packages instead of touring everything\n- close with what the reader can now do, not a recap\n\n## Related Skills\n\n- `codebase-onboarding`\n- `coding-standards`\n- `council`\n- official upstream format: `microsoft\u002Fcodetour`\n","# Code Tour\n\nCreate **CodeTour** `.tour` files for codebase walkthroughs that open directly to real files and line ranges. Tours live in `.tours\u002F` and are meant for the CodeTour format, not ad hoc Markdown notes.\n\nA good tour is a narrative for a specific reader:\n- what they are looking at\n- why it matters\n- what path they should follow next\n\nOnly create `.tour` JSON files. Do not modify source code as part of this skill.\n\n## When to Use\n\nUse this skill when:\n- the user asks for a code tour, onboarding tour, architecture walkthrough, or PR tour\n- the user says \"explain how X works\" and wants a reusable guided artifact\n- the user wants a ramp-up path for a new engineer or reviewer\n- the task is better served by a guided sequence than a flat summary\n\nExamples:\n- onboarding a new maintainer\n- architecture tour for one service or package\n- PR-review walk-through anchored to changed files\n- RCA tour showing the failure path\n- security review tour of trust boundaries and key checks\n\n## When NOT to Use\n\n| Instead of code-tour | Use |\n| --- | --- |\n| A one-off explanation in chat is enough | answer directly |\n| The user wants prose docs, not a `.tour` artifact | `documentation-lookup` or repo docs editing |\n| The task is implementation or refactoring | do the implementation work |\n| The task is broad codebase onboarding without a tour artifact | `codebase-onboarding` |\n\n## Workflow\n\n### 1. Discover\n\nExplore the repo before writing anything:\n- README and package\u002Fapp entry points\n- folder structure\n- relevant config files\n- the changed files if the tour is PR-focused\n\nDo not start writing steps before you understand the shape of the code.\n\n### 2. Infer the reader\n\nDecide the persona and depth from the request.\n\n| Request shape | Persona | Suggested depth |\n| --- | --- | --- |\n| \"onboarding\", \"new joiner\" | `new-joiner` | 9-13 steps |\n| \"quick tour\", \"vibe check\" | `vibecoder` | 5-8 steps |\n| \"architecture\" | `architect` | 14-18 steps |\n| \"tour this PR\" | `pr-reviewer` | 7-11 steps |\n| \"why did this break\" | `rca-investigator` | 7-11 steps |\n| \"security review\" | `security-reviewer` | 7-11 steps |\n| \"explain how this feature works\" | `feature-explainer` | 7-11 steps |\n| \"debug this path\" | `bug-fixer` | 7-11 steps |\n\n### 3. Read and verify anchors\n\nEvery file path and line anchor must be real:\n- confirm the file exists\n- confirm the line numbers are in range\n- if using a selection, verify the exact block\n- if the file is volatile, prefer a pattern-based anchor\n\nNever guess line numbers.\n\n### 4. Write the `.tour`\n\nWrite to:\n\n```text\n.tours\u002F\u003Cpersona>-\u003Cfocus>.tour\n```\n\nKeep the path deterministic and readable.\n\n### 5. Validate\n\nBefore finishing:\n- every referenced path exists\n- every line or selection is valid\n- the first step is anchored to a real file or directory\n- the `ref` points at a branch or commit that actually has every file the tour references (see below)\n- the tour tells a coherent story rather than listing files\n\n## The `ref` Field\n\n`ref` ties the tour to a git branch or commit. It matters more than it looks: when `ref` is not the branch the reader has checked out, CodeTour opens each step's file from that revision in git, not from the files on disk. If a file is not in that revision, the step will not open — the reader sees *\"The editor could not be opened because the file was not found\"* even though the file is sitting right there. The tour and its comments still show, so the real cause is easy to miss.\n\nPick `ref` by tour type:\n\n| Tour type | Set `ref` to |\n| --- | --- |\n| PR tour | the PR branch — never the base branch |\n| Onboarding \u002F architecture | the branch the reader will be on (often `main`), or leave it out |\n| Not sure | leave `ref` out, so CodeTour reads files straight from disk |\n\nThe PR case is the common trap: a PR usually adds new files, and new files do not exist on the base branch yet. Point `ref` at the base (e.g. `develop`) and every step on a new file fails to open.\n\nBefore finishing, confirm each step's file actually exists at the `ref` you chose.\n\n## Step Types\n\n### Content\n\nUse sparingly, usually only for a closing step:\n\n```json\n{ \"title\": \"Next Steps\", \"description\": \"You can now trace the request path end to end.\" }\n```\n\nDo not make the first step content-only.\n\n### Directory\n\nUse to orient the reader to a module:\n\n```json\n{ \"directory\": \"src\u002Fservices\", \"title\": \"Service Layer\", \"description\": \"The core orchestration logic lives here.\" }\n```\n\n### File + line\n\nThis is the default step type:\n\n```json\n{ \"file\": \"src\u002Fauth\u002Fmiddleware.ts\", \"line\": 42, \"title\": \"Auth Gate\", \"description\": \"Every protected request passes here first.\" }\n```\n\n### Selection\n\nUse when one code block matters more than the whole file:\n\n```json\n{\n  \"file\": \"src\u002Fcore\u002Fpipeline.ts\",\n  \"selection\": {\n    \"start\": { \"line\": 15, \"character\": 0 },\n    \"end\": { \"line\": 34, \"character\": 0 }\n  },\n  \"title\": \"Request Pipeline\",\n  \"description\": \"This block wires validation, auth, and downstream execution.\"\n}\n```\n\n### Pattern\n\nUse when exact lines may drift:\n\n```json\n{ \"file\": \"src\u002Fapp.ts\", \"pattern\": \"export default class App\", \"title\": \"Application Entry\" }\n```\n\n### URI\n\nUse for PRs, issues, or docs when helpful:\n\n```json\n{ \"uri\": \"https:\u002F\u002Fgithub.com\u002Forg\u002Frepo\u002Fpull\u002F456\", \"title\": \"The PR\" }\n```\n\n## Writing Rule: SMIG\n\nEach description should answer:\n- **Situation**: what the reader is looking at\n- **Mechanism**: how it works\n- **Implication**: why it matters for this persona\n- **Gotcha**: what a smart reader might miss\n\nKeep descriptions compact, specific, and grounded in the actual code.\n\n## Narrative Shape\n\nUse this arc unless the task clearly needs something different:\n1. orientation\n2. module map\n3. core execution path\n4. edge case or gotcha\n5. closing \u002F next move\n\nThe tour should feel like a path, not an inventory.\n\n## Example\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Faka.ms\u002Fcodetour-schema\",\n  \"title\": \"API Service Tour\",\n  \"description\": \"Walkthrough of the request path for the payments service.\",\n  \"ref\": \"main\",\n  \"steps\": [\n    {\n      \"directory\": \"src\",\n      \"title\": \"Source Root\",\n      \"description\": \"All runtime code for the service starts here.\"\n    },\n    {\n      \"file\": \"src\u002Fserver.ts\",\n      \"line\": 12,\n      \"title\": \"Entry Point\",\n      \"description\": \"The server boots here and wires middleware before any route is reached.\"\n    },\n    {\n      \"file\": \"src\u002Froutes\u002Fpayments.ts\",\n      \"line\": 8,\n      \"title\": \"Payment Routes\",\n      \"description\": \"Every payments request enters through this router before hitting service logic.\"\n    },\n    {\n      \"title\": \"Next Steps\",\n      \"description\": \"You can now follow any payment request end to end with the main anchors in place.\"\n    }\n  ]\n}\n```\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n| --- | --- |\n| Flat file listing | Tell a story with dependency between steps |\n| Generic descriptions | Name the concrete code path or pattern |\n| Guessed anchors | Verify every file and line first |\n| Too many steps for a quick tour | Cut aggressively |\n| First step is content-only | Anchor the first step to a real file or directory |\n| Persona mismatch | Write for the actual reader, not a generic engineer |\n\n## Best Practices\n\n- keep step count proportional to repo size and persona depth\n- use directory steps for orientation, file steps for substance\n- for PR tours, cover changed files first\n- for monorepos, scope to the relevant packages instead of touring everything\n- close with what the reader can now do, not a recap\n\n## Related Skills\n\n- `codebase-onboarding`\n- `coding-standards`\n- `council`\n- official upstream format: `microsoft\u002Fcodetour`\n",{"name":5,"metadata":54,"description":7},{"origin":55},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fcode-tour",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill code-tour",{"tool":70,"command":71},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill code-tour",{"tool":73,"command":74},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill code-tour","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcode-tour\u002FSKILL.md",true,[],[79,87,95,102,109,116],{"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":86},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"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":94},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":94},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":94},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":94},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":94},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]