[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACJNFT2MMYBT8WFBJR8HXM":3,"skill-same:01M6ACJNFT2MMYBT8WFBJR8HXM":67},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6ACJNFT2MMYBT8WFBJR8HXM","merging-dependabot-prs",null,"Use when triaging, classifying or landing Dependabot pull requests in this repo — clearing the open Dependabot queue, deciding whether a bump needs a WW Jira ticket, or checking whether a bump's build actually passed.","apache\u002Fstruts","apache","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4","01M6AC83E6K4FDKK7HZ8WNMQKE","The Apache Software Foundation","01M6ACJC9PH86ZGJ487XPD32BP",1373,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmerging-dependabot-prs\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"prs","merging dependabot prs","dependabot","queue","when","requests","ticket","ww","jira ticket","build","bump","pull requests","use","landing","repo","open","pull","jira","2026-11-10 10:12:30",false,"---\nname: emitter-prep-for-pr\ndescription: >\n  Prepare language emitter changes for PR: validate (build, format, lint), add\n  a changeset, and push. This skill is specifically for the language emitter\n  packages (http-client-python, http-client-csharp, http-client-java) - NOT for\n  core TypeSpec packages like compiler, http, openapi3, etc. Use when the user\n  wants to finalize emitter changes, says things like \"prep for pr\", \"prepare\n  for PR\", \"validate and push\", \"add changeset\", or \"finalize changes\".\n---\n\n# Emitter Prep for PR\n\nPrepares language emitter changes for pull request by running build\u002Fformat\u002Flint,\nchecking for a changeset, and pushing to the remote branch.\n\n**This skill is for language emitter packages only:**\n\n- `http-client-python`\n- `http-client-csharp`\n- `http-client-java`\n\nDo NOT use this skill for core TypeSpec packages (compiler, http, openapi3, etc.).\n\n## Workflow\n\n### Step 1: Determine the emitter package\n\nFigure out which emitter package the user is working on from context (cwd, recent\nchanges, or ask). The package will be under `packages\u002F\u003Cpackage-name>\u002F`.\n\n### Step 2: Build, format, and lint the emitter package\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002FPACKAGE_NAME\n\n# Build\nnpm run build\n\n# Format (includes both TypeScript and Python formatting)\nnpm run format\n\n# Lint (emitter-only is fine for quick validation)\nnpm run lint -- --emitter\n```\n\nIf any step fails, report the error and stop. Do not proceed.\n\n### Step 3: Run format at repo root\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\npnpm format\n```\n\n**Important:** `pnpm format` may touch files outside the emitter package (e.g.,\n`.devcontainer\u002F`, other packages). When staging changes in Step 6, **only stage\nfiles within the emitter package directory** (`packages\u002FPACKAGE_NAME\u002F`) and\n`.chronus\u002Fchanges\u002F` and `.github\u002Fskills\u002F`. Discard any formatting changes to\nunrelated files with `git checkout -- \u003Cfile>`.\n\n### Step 4: Check for existing changeset\n\nCheck if a changeset already exists for the current branch:\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\nls .chronus\u002Fchanges\u002F | grep -i \"$BRANCH\" || echo \"NO_CHANGESET\"\n```\n\n- If a changeset **exists**: Skip to Step 6 (no need to create one).\n- If **NO_CHANGESET**: Proceed to Step 5 to create one.\n\n### Step 5: Create changeset (only if none exists)\n\nAsk the user what kind of change this is, or infer from context:\n\n1. **changeKind** - one of: `internal`, `fix`, `feature`, `deprecation`, `breaking`, `dependencies`\n2. **message** - concise user-focused description\n\nThen create the file:\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\nTIMESTAMP=$(date +\"%Y-%m-%d-%H-%M-%S\")\nFILENAME=\".chronus\u002Fchanges\u002F${BRANCH}-${TIMESTAMP}.md\"\n```\n\n```markdown\n---\nchangeKind: \u003CKIND>\npackages:\n  - \"\u003CPACKAGE>\"\n---\n\n\u003CMESSAGE>\n```\n\n### Step 6: Stage, commit, and push\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\ngit add -A\ngit status\n```\n\nShow the user what will be committed and ask for confirmation. Then:\n\n```bash\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\ngit commit -m \"\u003CCOMMIT_MESSAGE>\n\nCo-authored-by: Copilot \u003C223556219+Copilot@users.noreply.github.com>\"\n\n# Always push to origin (user's fork), never upstream\ngit push origin \"$BRANCH\"\n```\n\n## Changeset Guidelines\n\n### changeKind reference\n\n- **internal**: Tests, CI\u002FCD, refactoring, docs, skills — not user-facing\n- **fix**: Bug fixes users would notice\n- **feature**: New user-facing capabilities\n- **deprecation**: Marking something as deprecated\n- **breaking**: Removing or changing behavior incompatibly\n- **dependencies**: Dependency version bumps\n\n### Message examples\n\n- `internal`: \"Improve CI pipeline performance and test infrastructure\"\n- `fix`: \"Fix incorrect deserialization of nullable enum properties\"\n- `feature`: \"Add support for XML serialization in request bodies\"\n\n### Package names\n\n| Folder               | Package Name                   |\n| -------------------- | ------------------------------ |\n| `http-client-python` | `@typespec\u002Fhttp-client-python` |\n| `http-client-csharp` | `@typespec\u002Fhttp-client-csharp` |\n| `http-client-java`   | `@typespec\u002Fhttp-client-java`   |\n","# Emitter Prep for PR\n\nPrepares language emitter changes for pull request by running build\u002Fformat\u002Flint,\nchecking for a changeset, and pushing to the remote branch.\n\n**This skill is for language emitter packages only:**\n\n- `http-client-python`\n- `http-client-csharp`\n- `http-client-java`\n\nDo NOT use this skill for core TypeSpec packages (compiler, http, openapi3, etc.).\n\n## Workflow\n\n### Step 1: Determine the emitter package\n\nFigure out which emitter package the user is working on from context (cwd, recent\nchanges, or ask). The package will be under `packages\u002F\u003Cpackage-name>\u002F`.\n\n### Step 2: Build, format, and lint the emitter package\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\u002Fpackages\u002FPACKAGE_NAME\n\n# Build\nnpm run build\n\n# Format (includes both TypeScript and Python formatting)\nnpm run format\n\n# Lint (emitter-only is fine for quick validation)\nnpm run lint -- --emitter\n```\n\nIf any step fails, report the error and stop. Do not proceed.\n\n### Step 3: Run format at repo root\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\npnpm format\n```\n\n**Important:** `pnpm format` may touch files outside the emitter package (e.g.,\n`.devcontainer\u002F`, other packages). When staging changes in Step 6, **only stage\nfiles within the emitter package directory** (`packages\u002FPACKAGE_NAME\u002F`) and\n`.chronus\u002Fchanges\u002F` and `.github\u002Fskills\u002F`. Discard any formatting changes to\nunrelated files with `git checkout -- \u003Cfile>`.\n\n### Step 4: Check for existing changeset\n\nCheck if a changeset already exists for the current branch:\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\nls .chronus\u002Fchanges\u002F | grep -i \"$BRANCH\" || echo \"NO_CHANGESET\"\n```\n\n- If a changeset **exists**: Skip to Step 6 (no need to create one).\n- If **NO_CHANGESET**: Proceed to Step 5 to create one.\n\n### Step 5: Create changeset (only if none exists)\n\nAsk the user what kind of change this is, or infer from context:\n\n1. **changeKind** - one of: `internal`, `fix`, `feature`, `deprecation`, `breaking`, `dependencies`\n2. **message** - concise user-focused description\n\nThen create the file:\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\nTIMESTAMP=$(date +\"%Y-%m-%d-%H-%M-%S\")\nFILENAME=\".chronus\u002Fchanges\u002F${BRANCH}-${TIMESTAMP}.md\"\n```\n\n```markdown\n---\nchangeKind: \u003CKIND>\npackages:\n  - \"\u003CPACKAGE>\"\n---\n\n\u003CMESSAGE>\n```\n\n### Step 6: Stage, commit, and push\n\n```bash\ncd ~\u002FDesktop\u002Fgithub\u002Ftypespec\ngit add -A\ngit status\n```\n\nShow the user what will be committed and ask for confirmation. Then:\n\n```bash\nBRANCH=$(git rev-parse --abbrev-ref HEAD)\ngit commit -m \"\u003CCOMMIT_MESSAGE>\n\nCo-authored-by: Copilot \u003C223556219+Copilot@users.noreply.github.com>\"\n\n# Always push to origin (user's fork), never upstream\ngit push origin \"$BRANCH\"\n```\n\n## Changeset Guidelines\n\n### changeKind reference\n\n- **internal**: Tests, CI\u002FCD, refactoring, docs, skills — not user-facing\n- **fix**: Bug fixes users would notice\n- **feature**: New user-facing capabilities\n- **deprecation**: Marking something as deprecated\n- **breaking**: Removing or changing behavior incompatibly\n- **dependencies**: Dependency version bumps\n\n### Message examples\n\n- `internal`: \"Improve CI pipeline performance and test infrastructure\"\n- `fix`: \"Fix incorrect deserialization of nullable enum properties\"\n- `feature`: \"Add support for XML serialization in request bodies\"\n\n### Package names\n\n| Folder               | Package Name                   |\n| -------------------- | ------------------------------ |\n| `http-client-python` | `@typespec\u002Fhttp-client-python` |\n| `http-client-csharp` | `@typespec\u002Fhttp-client-csharp` |\n| `http-client-java`   | `@typespec\u002Fhttp-client-java`   |\n",{"name":42,"description":43},"emitter-prep-for-pr","Prepare language emitter changes for PR: validate (build, format, lint), add a changeset, and push. This skill is specifically for the language emitter packages (http-client-python, http-client-csharp, http-client-java) - NOT for core TypeSpec packages like compiler, http, openapi3, etc. Use when the user wants to finalize emitter changes, says things like \"prep for pr\", \"prepare for PR\", \"validate and push\", \"add changeset\", or \"finalize changes\".","main","05b9bad7c57b9b58e8fb5390f9bab081a1a9ac31",".claude\u002Fskills\u002Fmerging-dependabot-prs",876,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts","https:\u002F\u002Fstruts.apache.org\u002F","https:\u002F\u002Fgithub.com\u002Fapache","https:\u002F\u002Fwww.apache.org\u002F","2026-11-14 17:00:41",{"source":8,"skillName":42,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add apache\u002Fstruts --skill emitter-prep-for-pr",{"tool":59,"command":60},"bunx","bunx skills add apache\u002Fstruts --skill emitter-prep-for-pr",{"tool":62,"command":63},"pnpm","pnpm dlx skills add apache\u002Fstruts --skill emitter-prep-for-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmerging-dependabot-prs\u002FSKILL.md",true,[],[68,104,130,148,167,185],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":87,"publishedAt":37},"01M6ACJVHR7YZNC8AZFK987QP0","code-review","Apache Struts pull request review guide. Use when reviewing pull requests in this repository to check test conventions, security-sensitive framework code, PR and commit hygiene, and Struts-specific implementation patterns.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcode-review\u002FSKILL.md",[74,79,82],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":80,"categoryName":81,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[88,89,90,35,30,91,9,92,93,94,95,96,97,98,99,31,100,23,101,24,102,103],"code review","code","review","test","pr","pull request","struts","security","commit","framework","Test Conventions","review guide","pull request review","check","request","repository",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":113,"publishedAt":37},"01M6ACJSK2MWX4MPVHH4S3FK0V","triaging-security-reports","Use when a vulnerability or security report arrives for triage, when assessing a CVE\u002FRCE\u002FOGNL\u002Finjection claim against the code, when deciding whether a finding is the framework's fault or the application's, when drafting a reply to a security researcher, or when a claim that is already public (a Full Disclosure post, a blog, a scanner advisory) needs the project's position stated for users and scanner vendors — to research the claim from source without trusting the reporter and without fabricating your own facts.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftriaging-security-reports\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000021","资料检索与研究",[114,95,115,89,116,117,118,119,31,120,121,122,123,124,23,125,126,97,127,128,129],"triaging security reports","reports","cve","for","security report","claim","vulnerability","facts","injection","source","project","scanner","full","advisory","users","drafting",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":37},"01M6ACJQJRMWRPQJ7P796RJZDZ","releasing-struts","Use when running or planning an Apache Struts release on any maintenance line (6.x, 7.x) - cutting the tag, staging artifacts, opening the vote, promoting, updating the site and announcing - or when asked what the next step in a release is.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Freleasing-struts\u002FSKILL.md",[],[94,137,9,138,139,140,141,31,23,142,143,144,145,146,147],"releasing struts","planning","artifacts","release","running","maintenance","next","what the","line","site","next step",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":37},"01M6ACJK00H307C0B4HTMM34EB","creating-version-notes","Use when preparing, updating, or reviewing the release documentation for a Struts release or release candidate on any maintenance line (6.x, 7.x) - the Version Notes page on the cwiki, its Migration Guide entry, the GitHub release notes, and the test-build announcement mail.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreating-version-notes\u002FSKILL.md",[],[155,156,157,158,91,159,160,140,161,94,23,162,163,145,164,165,117,166,31,142],"notes","creating version notes","version","documentation","announcement","github","release notes","candidate","mail","guide","github release","page",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":37},"01M6ACJGZAS1WB8RHDQMC76XFB","creating-security-bulletins","Use when drafting, updating, or reviewing an S2-XXX security bulletin on the Struts cwiki, when preparing bulletin text ahead of a CVE request, when filling a CVE record in the ASF CVE tool (cveprocess.apache.org \u002F Vulnogram), when deciding when to publish, when publishing a bulletin and announcing it to the ASF lists, when wrapping up after the advisory mails, or when deciding how much detail about a fixed vulnerability is safe to publish.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreating-security-bulletins\u002FSKILL.md",[],[95,174,94,9,175,176,23,129,120,177,178,179,102,180,181,116,182,183,31,184],"creating security bulletins","safe","up","text","publish","how","asf","org","tool","publishing","detail",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":37},"01M6ACJERGEM6AYZGCC6A2ZC27","creating-release-vote-mail","Use when opening the formal release vote for a Struts release candidate on any maintenance line (6.x, 7.x) - composing and drafting the [VOTE] Apache Struts X.Y.Z mail to dev@ once the Version Notes page, GitHub release and staged artifacts are published.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fstruts\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcreating-release-vote-mail\u002FSKILL.md",[],[192,140,163,155,193,9,160,139,117,166,31,94,23,157,129,162,142,145,194,165],"creating release vote mail","dev","staged"]