[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD54D8Z4HHTF9XYYG56B27":3,"skill-same:01M6AD54D8Z4HHTF9XYYG56B27":61},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6AD54D8Z4HHTF9XYYG56B27","developer",null,"Core developer rules and coding conventions for gh-aw changes.","github\u002Fgh-aw","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3VCZ4WKQSFSRTPN7N9DN",5636,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdeveloper\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[5,24,25,26,27,28,29,30,31],"core","for","gh","coding conventions","Rules","changes","conventions","coding","2026-11-10 10:12:30",false,"---\nname: developer\ndescription: Core developer rules and coding conventions for gh-aw changes.\n---\n\n\n# Developer Instructions\n\nUse this reference for gh-aw technical specs and development guidelines across code organization, validation, security, and implementation patterns.\n\n## Table of Contents\n\n- [Operational Command Playbook](#operational-command-playbook)\n- [Capitalization Guidelines](#capitalization-guidelines)\n- [Sub-Skills](#sub-skills)\n\n\n## Operational Command Playbook\n\nUse this section for the detailed day-to-day command flow that was intentionally removed from `AGENTS.md` to keep first-run ambient context small.\n\n### Validation checkpoints\n\nRun validation in tiers. Keep formatting and focused tests in the inner loop;\ndefer package-wide Go linting and workflow drift to the final pass.\n\n1. **After each significant code edit** (format changed files, then run one focused check)\n   ```bash\n   make fmt\n   go test .\u002Fpkg\u002Fcli -run '^TestRelevantBehavior' -count=1\n   ```\n   Replace the package and test pattern with the behavior being changed. This\n   compiles the affected package too; do not add a CLI build unless the next\n   command needs `.\u002Fgh-aw`. First builds after Go edits can exceed the warm-cache\n   budget because Go compiles the entire package, including its test files.\n2. **Before every intermediate `report_progress` call** (fast, no test bodies)\n   ```bash\n   make agent-report-progress-no-test\n   ```\n   This formats branch changes and compiles\u002Fvets changed Go packages. It does\n   not link the CLI or run package-wide Go linters or workflow recompilation.\n   Schema changes still rebuild the CLI; stale-lock and local-permission guards\n   still run. JavaScript\u002Faction-shell checks remain change-scoped.\n3. **Before the FINAL `report_progress` call** (build, lint, impacted tests, and workflow drift)\n   ```bash\n   make agent-report-progress\n   ```\n   This is the full pre-PR gate. Run it once, not after every focused test.\n   `make agent-finish` is an explicit repository-wide maintenance sweep, not an\n   inner-loop or routine handoff command.\n\n> **Key rule:** Run `test-unit` only before the **final** `report_progress` call, not before intermediate saves. Intermediate saves defer full Go lint and workflow drift; they do not replace the final gate.\n\n> **Timeout budget:** Aim for warm-cache intermediate validation under 5 seconds. The 30-second `test-unit` budget covers selected test runtime, not compilation, linting, or full workflow drift; the final gate can take minutes. Set `TEST_UNIT_RUN_FULL=1` only when the full Go suite is required.\n\n### Change-type command matrix\n\n- Formatting: `make fmt` formats branch changes (including staged, unstaged, and untracked files). Go-only edits do not need npm. Use `make fmt-all` only for an explicit full-repository formatting sweep.\n- Workflow markdown changes: `make recompile`\n- JavaScript (`*.cjs`) changes: `make fmt`, then a focused runtime test. The intermediate gate runs changed-file JavaScript lint.\n\n### Common focused checks from recent repository work\n\n- `pkg\u002Fworkflow\u002F` edits: run `go test .\u002Fpkg\u002Fworkflow -count=1` during iteration; narrow with `-run` when only one workflow behavior is under active change.\n- `actions\u002Fsetup\u002Fjs\u002F` edits: after `make fmt`, run the targeted `actions\u002Fsetup\u002Fjs\u002F*.test.cjs` suites for the files you touched. Gateway changes commonly validate with `npx vitest run actions\u002Fsetup\u002Fjs\u002Fstart_mcp_gateway.test.cjs`.\n- Workflow source changes that also touch compiler or runtime code: run `make recompile`, then rerun the affected focused Go or JavaScript checks before the final `make agent-report-progress`.\n\n### Merge-main playbook\n\nWhen explicitly asked to merge main:\n\n1. Run `make merge-main`.\n2. If conflicts exist in `.go` or `.cjs`, resolve and stage files.\n3. Run:\n   ```bash\n   make build\n   make recompile\n   git commit\n   make fmt\n   ```\n\n## Capitalization Guidelines\n\nThe gh-aw CLI follows context-based capitalization to distinguish between the product name and generic workflow references.\n\n### Capitalization Rules\n\n| Context | Format | Example |\n|---------|--------|---------|\n| Product name | **Capitalized** | \"GitHub Agentic Workflows CLI from GitHub Next\" |\n| Generic workflows | **Lowercase** | \"Enable agentic workflows\" |\n| Technical terms | **Capitalized** | \"Compile Markdown workflows to GitHub Actions YAML\" |\n\nThis convention distinguishes between the product name (GitHub Agentic Workflows) and the concept (agentic workflows), following industry standards similar to \"GitHub Actions\" vs. \"actions\".\n\n### Implementation\n\nThe capitalization rules are enforced through automated tests in `cmd\u002Fgh-aw\u002Fcapitalization_test.go` that run as part of the standard test suite.\n\n\n\n## Sub-Skills\n\nThe following sub-skills cover specific areas of the codebase. Load them lazily when the task requires the specific domain:\n\n| Sub-skill | When to use |\n|-----------|-------------|\n| `.github\u002Fskills\u002Fdeveloper-code-organization\u002FSKILL.md` | Creating new files, refactoring, WASM stubs, file size decisions |\n| `.github\u002Fskills\u002Fdeveloper-security\u002FSKILL.md` | Implementing new features, reviewing for security, template injection concerns |\n| `.github\u002Fskills\u002Fdeveloper-internals\u002FSKILL.md` | Working on compiler internals, validation, safe outputs, MCP server, schema changes |\n| `.github\u002Fskills\u002Fdeveloper-release\u002FSKILL.md` | Creating a release, evaluating breaking changes, firewall log analysis |\n","# Developer Instructions\n\nUse this reference for gh-aw technical specs and development guidelines across code organization, validation, security, and implementation patterns.\n\n## Table of Contents\n\n- [Operational Command Playbook](#operational-command-playbook)\n- [Capitalization Guidelines](#capitalization-guidelines)\n- [Sub-Skills](#sub-skills)\n\n\n## Operational Command Playbook\n\nUse this section for the detailed day-to-day command flow that was intentionally removed from `AGENTS.md` to keep first-run ambient context small.\n\n### Validation checkpoints\n\nRun validation in tiers. Keep formatting and focused tests in the inner loop;\ndefer package-wide Go linting and workflow drift to the final pass.\n\n1. **After each significant code edit** (format changed files, then run one focused check)\n   ```bash\n   make fmt\n   go test .\u002Fpkg\u002Fcli -run '^TestRelevantBehavior' -count=1\n   ```\n   Replace the package and test pattern with the behavior being changed. This\n   compiles the affected package too; do not add a CLI build unless the next\n   command needs `.\u002Fgh-aw`. First builds after Go edits can exceed the warm-cache\n   budget because Go compiles the entire package, including its test files.\n2. **Before every intermediate `report_progress` call** (fast, no test bodies)\n   ```bash\n   make agent-report-progress-no-test\n   ```\n   This formats branch changes and compiles\u002Fvets changed Go packages. It does\n   not link the CLI or run package-wide Go linters or workflow recompilation.\n   Schema changes still rebuild the CLI; stale-lock and local-permission guards\n   still run. JavaScript\u002Faction-shell checks remain change-scoped.\n3. **Before the FINAL `report_progress` call** (build, lint, impacted tests, and workflow drift)\n   ```bash\n   make agent-report-progress\n   ```\n   This is the full pre-PR gate. Run it once, not after every focused test.\n   `make agent-finish` is an explicit repository-wide maintenance sweep, not an\n   inner-loop or routine handoff command.\n\n> **Key rule:** Run `test-unit` only before the **final** `report_progress` call, not before intermediate saves. Intermediate saves defer full Go lint and workflow drift; they do not replace the final gate.\n\n> **Timeout budget:** Aim for warm-cache intermediate validation under 5 seconds. The 30-second `test-unit` budget covers selected test runtime, not compilation, linting, or full workflow drift; the final gate can take minutes. Set `TEST_UNIT_RUN_FULL=1` only when the full Go suite is required.\n\n### Change-type command matrix\n\n- Formatting: `make fmt` formats branch changes (including staged, unstaged, and untracked files). Go-only edits do not need npm. Use `make fmt-all` only for an explicit full-repository formatting sweep.\n- Workflow markdown changes: `make recompile`\n- JavaScript (`*.cjs`) changes: `make fmt`, then a focused runtime test. The intermediate gate runs changed-file JavaScript lint.\n\n### Common focused checks from recent repository work\n\n- `pkg\u002Fworkflow\u002F` edits: run `go test .\u002Fpkg\u002Fworkflow -count=1` during iteration; narrow with `-run` when only one workflow behavior is under active change.\n- `actions\u002Fsetup\u002Fjs\u002F` edits: after `make fmt`, run the targeted `actions\u002Fsetup\u002Fjs\u002F*.test.cjs` suites for the files you touched. Gateway changes commonly validate with `npx vitest run actions\u002Fsetup\u002Fjs\u002Fstart_mcp_gateway.test.cjs`.\n- Workflow source changes that also touch compiler or runtime code: run `make recompile`, then rerun the affected focused Go or JavaScript checks before the final `make agent-report-progress`.\n\n### Merge-main playbook\n\nWhen explicitly asked to merge main:\n\n1. Run `make merge-main`.\n2. If conflicts exist in `.go` or `.cjs`, resolve and stage files.\n3. Run:\n   ```bash\n   make build\n   make recompile\n   git commit\n   make fmt\n   ```\n\n## Capitalization Guidelines\n\nThe gh-aw CLI follows context-based capitalization to distinguish between the product name and generic workflow references.\n\n### Capitalization Rules\n\n| Context | Format | Example |\n|---------|--------|---------|\n| Product name | **Capitalized** | \"GitHub Agentic Workflows CLI from GitHub Next\" |\n| Generic workflows | **Lowercase** | \"Enable agentic workflows\" |\n| Technical terms | **Capitalized** | \"Compile Markdown workflows to GitHub Actions YAML\" |\n\nThis convention distinguishes between the product name (GitHub Agentic Workflows) and the concept (agentic workflows), following industry standards similar to \"GitHub Actions\" vs. \"actions\".\n\n### Implementation\n\nThe capitalization rules are enforced through automated tests in `cmd\u002Fgh-aw\u002Fcapitalization_test.go` that run as part of the standard test suite.\n\n\n\n## Sub-Skills\n\nThe following sub-skills cover specific areas of the codebase. Load them lazily when the task requires the specific domain:\n\n| Sub-skill | When to use |\n|-----------|-------------|\n| `.github\u002Fskills\u002Fdeveloper-code-organization\u002FSKILL.md` | Creating new files, refactoring, WASM stubs, file size decisions |\n| `.github\u002Fskills\u002Fdeveloper-security\u002FSKILL.md` | Implementing new features, reviewing for security, template injection concerns |\n| `.github\u002Fskills\u002Fdeveloper-internals\u002FSKILL.md` | Working on compiler internals, validation, safe outputs, MCP server, schema changes |\n| `.github\u002Fskills\u002Fdeveloper-release\u002FSKILL.md` | Creating a release, evaluating breaking changes, firewall log analysis |\n",{"name":5,"description":7},"main","e80177a47be55dbcaab13d0630a690e6983a8238",".github\u002Fskills\u002Fdeveloper",626,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw","https:\u002F\u002Fgh.io\u002Fgh-aw","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-15 06:45:15",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add github\u002Fgh-aw --skill developer",{"tool":53,"command":54},"bunx","bunx skills add github\u002Fgh-aw --skill developer",{"tool":56,"command":57},"pnpm","pnpm dlx skills add github\u002Fgh-aw --skill developer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdeveloper\u002FSKILL.md",true,[],[62,70,78,105,123,147],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":69},"01M7DQYVZ9W9DDXKQ9452SNP8J","cracktro","Edit, preview, and verify the standalone interactive talk deck in docs\u002Fpublic\u002Fcracktro (slides, SVG diagrams, transitions, WebAudio sound).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcracktro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":77},"01M7612HQ4378TK8QZ5HPAF4KR","create-connector","Create or extend a declaration-only third-party connector, with narrow reads, separate safe outputs, optional protected triggers, and offline conformance evidence.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcreate-connector\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":92,"publishedAt":32},"01M6ADC942STTXHFV410J4DH0X","GitHub Agentic Workflows","GitHub Agentic Workflows (`gh-aw`) is a GitHub CLI extension for writing Agentic Workflows in markdown and compiling them to GitHub Actions.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002FSKILL.md",[84,89],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":90,"categoryName":91,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000023","Skill与智能体开发",[9,93,94,95,96,97,98,99,100,26,25,101,102,103,104],"github agentic workflows","agentic workflows","workflows","agentic","extension","markdown","github cli","cli","compiling","writing","github actions","actions",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":32},"01M6ADC6ZXSA46N9XD6VNAP1MS","windows-compatibility","Cross-platform path handling and command patterns","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fwindows-compatibility\u002FSKILL.md",[],[112,113,114,115,116,117,118,119,120,121,122],"windows","windows compatibility","compatibility","command","git","bugs","platform","high","patterns","cross-platform","path",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":32},"01M6ADC44957SVQF96R5YY247P","versioning-policy","Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[130,131,132,133,134,100,135,136,137,138,139,140,141,142,25,143,144,28,145,146],"versioning","policy","versioning policy","gate","implementation","workspace","pr","sdk","release","ci","npm","semver","squad","incident","incidents","version","resolution",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":157,"publishedAt":32},"01M6ADC1PHMEAEVR87F8PDR89X","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[153,156],{"categoryNo":154,"categoryName":155,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":90,"categoryName":91,"taxonomyType":87,"taxonomyTypeDesc":88},[158,159,160,161,162,163,164,165,166,167,168,169,170,25,171,172],"tiered memory","memory","performance","design","agent memory","proposal","cold","model","wiki","spawn","memory-management","context","three","runtime","management"]