[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F7T3JQ91ZP9BT6X98ZMW1K":3,"skill-same:01M7F7T3JQ91ZP9BT6X98ZMW1K":46},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7F7T3JQ91ZP9BT6X98ZMW1K","batch-orchestration",null,"Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fbatch-orchestration\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: batch-orchestration\ndescription: Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.\nuser-invocable: true\n---\n\n# Batch Orchestration\n\nThe `\u002Fbatch` command pattern for large-scale parallel changes.\n\n## How It Works\n\n```text\n\u002Fbatch \u003Cinstruction>\n  │\n  ├── 1. Research: scan repo, understand scope\n  ├── 2. Decompose: split into 5-30 independent units\n  ├── 3. Present plan: show units, ask for approval\n  ├── 4. Execute: one background agent per unit in isolated worktree\n  └── 5. Collect: each agent runs tests and opens a PR\n```\n\n## Syntax\n\n```bash\n\u002Fbatch Convert all React class components to function components\n\u002Fbatch Add error boundaries to every page component\n\u002Fbatch Migrate from moment.js to dayjs across the codebase\n\u002Fbatch Add OpenTelemetry tracing to all API handlers\n```\n\nThe instruction should describe the change pattern, not individual files. The batch system finds the files.\n\n## Phase 1: Research\n\nThe orchestrator scans the repo to find every instance that matches the instruction:\n\n```bash\ngrep -r \"class.*extends.*Component\" --include=\"*.tsx\" -l\n```\n\nIt builds a complete list of targets and groups them by independence.\n\n## Phase 2: Decompose\n\nEach unit must be:\n\n- **Independent** — no shared state with other units\n- **Self-contained** — can be implemented and tested alone\n- **Verifiable** — has a clear pass\u002Ffail criteria\n\n**Good units:**\n```text\nUnit 1: Convert src\u002Fcomponents\u002FHeader.tsx (class → function)\nUnit 2: Convert src\u002Fcomponents\u002FFooter.tsx (class → function)\nUnit 3: Convert src\u002Fcomponents\u002FSidebar.tsx (class → function)\n```\n\n**Bad units:**\n```text\nUnit 1: Convert all components in src\u002Fcomponents\u002F (too broad)\nUnit 2: Fix issues from Unit 1 (dependent)\n```\n\nTarget 5-30 units. Fewer than 5 doesn't justify the overhead. More than 30 and coordination costs grow.\n\n## Phase 3: Plan Approval\n\nThe orchestrator presents:\n\n```text\nBATCH: Convert class components to function components\n\nFound: 18 class components across src\u002F\n\nUnits (18):\n  1. src\u002Fcomponents\u002FHeader.tsx — class Header → function\n  2. src\u002Fcomponents\u002FFooter.tsx — class Footer → function\n  ...\n  18. src\u002Fpages\u002FSettings.tsx — class Settings → function\n\nPer unit: convert class to function, update hooks, run component tests\nEstimated: ~2 min per unit, ~5 min total (parallel)\n\nProceed? (y\u002Fn)\n```\n\n**Wait for approval.** Never spawn agents without explicit confirmation.\n\n## Phase 4: Execute\n\nAfter approval, for each unit:\n\n1. Create isolated git worktree\n2. Spawn background agent in that worktree\n3. Agent implements the change\n4. Agent runs relevant tests\n5. Agent opens a PR\n\nAgents run in parallel. Each has its own context window and worktree — no conflicts.\n\n```text\n[Agent 1] ── worktree-1 ── Header.tsx ── tests pass ── PR #41\n[Agent 2] ── worktree-2 ── Footer.tsx ── tests pass ── PR #42\n[Agent 3] ── worktree-3 ── Sidebar.tsx ── tests fail ── flagged\n```\n\n## Phase 5: Collect\n\nAfter all agents complete:\n\n- Summary of pass\u002Ffail per unit\n- Links to opened PRs\n- Any units that failed with error details\n- Failed units can be retried individually\n\n## Best For\n\n| Use Case | Why Batch Works |\n|----------|-----------------|\n| API migrations | Same pattern across many endpoints |\n| Dependency upgrades | Find\u002Freplace + fix across codebase |\n| Codemod-style refactors | Mechanical transformation, file by file |\n| Adding instrumentation | Same tracing\u002Flogging pattern everywhere |\n| Test coverage gaps | Add tests to untested modules independently |\n| Lint rule adoption | Apply new rule fixes across all files |\n\n## Anti-Patterns\n\n| Don't Batch | Why |\n|-------------|-----|\n| Interdependent changes | Units can't run in parallel if they depend on each other |\n| Shared state modifications | Multiple agents writing to the same config or state file |\n| Architecture changes | Need holistic reasoning, not file-by-file |\n| Schema migrations | Database changes must be sequential |\n| Changes requiring human judgment per file | Defeats the purpose of automation |\n\n## Relationship to Other Patterns\n\n| Pattern | Scale | Isolation |\n|---------|-------|-----------|\n| Direct edit | 1-3 files | None needed |\n| Subagent | 1 focused task | Forked context |\n| Worktree | 1 feature branch | Full repo copy |\n| Agent teams | 3-5 parallel tasks | Shared task list |\n| **Batch** | 5-30 identical pattern | Full worktree per unit |\n\nBatch is the heaviest tool. Use it when the change is mechanical, repetitive, and the units are truly independent.\n\n## Guardrails\n\n- Always review the decomposition before approving\n- Each agent must run tests before opening a PR\n- Failed units get flagged, not silently skipped\n- Clean up worktrees after all agents complete\n- Review PRs in batches — don't merge blindly\n","# Batch Orchestration\n\nThe `\u002Fbatch` command pattern for large-scale parallel changes.\n\n## How It Works\n\n```text\n\u002Fbatch \u003Cinstruction>\n  │\n  ├── 1. Research: scan repo, understand scope\n  ├── 2. Decompose: split into 5-30 independent units\n  ├── 3. Present plan: show units, ask for approval\n  ├── 4. Execute: one background agent per unit in isolated worktree\n  └── 5. Collect: each agent runs tests and opens a PR\n```\n\n## Syntax\n\n```bash\n\u002Fbatch Convert all React class components to function components\n\u002Fbatch Add error boundaries to every page component\n\u002Fbatch Migrate from moment.js to dayjs across the codebase\n\u002Fbatch Add OpenTelemetry tracing to all API handlers\n```\n\nThe instruction should describe the change pattern, not individual files. The batch system finds the files.\n\n## Phase 1: Research\n\nThe orchestrator scans the repo to find every instance that matches the instruction:\n\n```bash\ngrep -r \"class.*extends.*Component\" --include=\"*.tsx\" -l\n```\n\nIt builds a complete list of targets and groups them by independence.\n\n## Phase 2: Decompose\n\nEach unit must be:\n\n- **Independent** — no shared state with other units\n- **Self-contained** — can be implemented and tested alone\n- **Verifiable** — has a clear pass\u002Ffail criteria\n\n**Good units:**\n```text\nUnit 1: Convert src\u002Fcomponents\u002FHeader.tsx (class → function)\nUnit 2: Convert src\u002Fcomponents\u002FFooter.tsx (class → function)\nUnit 3: Convert src\u002Fcomponents\u002FSidebar.tsx (class → function)\n```\n\n**Bad units:**\n```text\nUnit 1: Convert all components in src\u002Fcomponents\u002F (too broad)\nUnit 2: Fix issues from Unit 1 (dependent)\n```\n\nTarget 5-30 units. Fewer than 5 doesn't justify the overhead. More than 30 and coordination costs grow.\n\n## Phase 3: Plan Approval\n\nThe orchestrator presents:\n\n```text\nBATCH: Convert class components to function components\n\nFound: 18 class components across src\u002F\n\nUnits (18):\n  1. src\u002Fcomponents\u002FHeader.tsx — class Header → function\n  2. src\u002Fcomponents\u002FFooter.tsx — class Footer → function\n  ...\n  18. src\u002Fpages\u002FSettings.tsx — class Settings → function\n\nPer unit: convert class to function, update hooks, run component tests\nEstimated: ~2 min per unit, ~5 min total (parallel)\n\nProceed? (y\u002Fn)\n```\n\n**Wait for approval.** Never spawn agents without explicit confirmation.\n\n## Phase 4: Execute\n\nAfter approval, for each unit:\n\n1. Create isolated git worktree\n2. Spawn background agent in that worktree\n3. Agent implements the change\n4. Agent runs relevant tests\n5. Agent opens a PR\n\nAgents run in parallel. Each has its own context window and worktree — no conflicts.\n\n```text\n[Agent 1] ── worktree-1 ── Header.tsx ── tests pass ── PR #41\n[Agent 2] ── worktree-2 ── Footer.tsx ── tests pass ── PR #42\n[Agent 3] ── worktree-3 ── Sidebar.tsx ── tests fail ── flagged\n```\n\n## Phase 5: Collect\n\nAfter all agents complete:\n\n- Summary of pass\u002Ffail per unit\n- Links to opened PRs\n- Any units that failed with error details\n- Failed units can be retried individually\n\n## Best For\n\n| Use Case | Why Batch Works |\n|----------|-----------------|\n| API migrations | Same pattern across many endpoints |\n| Dependency upgrades | Find\u002Freplace + fix across codebase |\n| Codemod-style refactors | Mechanical transformation, file by file |\n| Adding instrumentation | Same tracing\u002Flogging pattern everywhere |\n| Test coverage gaps | Add tests to untested modules independently |\n| Lint rule adoption | Apply new rule fixes across all files |\n\n## Anti-Patterns\n\n| Don't Batch | Why |\n|-------------|-----|\n| Interdependent changes | Units can't run in parallel if they depend on each other |\n| Shared state modifications | Multiple agents writing to the same config or state file |\n| Architecture changes | Need holistic reasoning, not file-by-file |\n| Schema migrations | Database changes must be sequential |\n| Changes requiring human judgment per file | Defeats the purpose of automation |\n\n## Relationship to Other Patterns\n\n| Pattern | Scale | Isolation |\n|---------|-------|-----------|\n| Direct edit | 1-3 files | None needed |\n| Subagent | 1 focused task | Forked context |\n| Worktree | 1 feature branch | Full repo copy |\n| Agent teams | 3-5 parallel tasks | Shared task list |\n| **Batch** | 5-30 identical pattern | Full worktree per unit |\n\nBatch is the heaviest tool. Use it when the change is mechanical, repetitive, and the units are truly independent.\n\n## Guardrails\n\n- Always review the decomposition before approving\n- Each agent must run tests before opening a PR\n- Failed units get flagged, not silently skipped\n- Clean up worktrees after all agents complete\n- Review PRs in batches — don't merge blindly\n",{"name":5,"description":7,"user-invocable":24},true,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Fbatch-orchestration",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill batch-orchestration",{"tool":39,"command":40},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill batch-orchestration",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill batch-orchestration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fbatch-orchestration\u002FSKILL.md",[],[47,54,59,66,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":55,"name":49,"nameZh":6,"description":50,"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},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\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},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\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},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\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},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\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},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]