merging-dependabot-prs
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.
- License 许可
- Apache-2.0
- 所属仓库
- apache/struts
- 最近更新
- 2026-11-14
- Stars
- ★ 1.4k
- Forks
- 876
01 前言 Front Matter
- name
- emitter-prep-for-pr
- description
- 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".
03 SKILL.md 正文
Emitter Prep for PR
Prepares language emitter changes for pull request by running build/format/lint, checking for a changeset, and pushing to the remote branch.
This skill is for language emitter packages only:
http-client-pythonhttp-client-csharphttp-client-java
Do NOT use this skill for core TypeSpec packages (compiler, http, openapi3, etc.).
Workflow
Step 1: Determine the emitter package
Figure out which emitter package the user is working on from context (cwd, recent
changes, or ask). The package will be under packages/<package-name>/.
Step 2: Build, format, and lint the emitter package
cd ~/Desktop/github/typespec/packages/PACKAGE_NAME
# Build
npm run build
# Format (includes both TypeScript and Python formatting)
npm run format
# Lint (emitter-only is fine for quick validation)
npm run lint -- --emitter
If any step fails, report the error and stop. Do not proceed.
Step 3: Run format at repo root
cd ~/Desktop/github/typespec
pnpm format
Important: pnpm format may touch files outside the emitter package (e.g.,
.devcontainer/, other packages). When staging changes in Step 6, only stage
files within the emitter package directory (packages/PACKAGE_NAME/) and
.chronus/changes/ and .github/skills/. Discard any formatting changes to
unrelated files with git checkout -- <file>.
Step 4: Check for existing changeset
Check if a changeset already exists for the current branch:
cd ~/Desktop/github/typespec
BRANCH=$(git rev-parse --abbrev-ref HEAD)
ls .chronus/changes/ | grep -i "$BRANCH" || echo "NO_CHANGESET"
- If a changeset exists: Skip to Step 6 (no need to create one).
- If NO_CHANGESET: Proceed to Step 5 to create one.
Step 5: Create changeset (only if none exists)
Ask the user what kind of change this is, or infer from context:
- changeKind - one of:
internal,fix,feature,deprecation,breaking,dependencies - message - concise user-focused description
Then create the file:
cd ~/Desktop/github/typespec
BRANCH=$(git rev-parse --abbrev-ref HEAD)
TIMESTAMP=$(date +"%Y-%m-%d-%H-%M-%S")
FILENAME=".chronus/changes/${BRANCH}-${TIMESTAMP}.md"
---
changeKind: <KIND>
packages:
- "<PACKAGE>"
---
<MESSAGE>
Step 6: Stage, commit, and push
cd ~/Desktop/github/typespec
git add -A
git status
Show the user what will be committed and ask for confirmation. Then:
BRANCH=$(git rev-parse --abbrev-ref HEAD)
git commit -m "<COMMIT_MESSAGE>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>"
# Always push to origin (user's fork), never upstream
git push origin "$BRANCH"
Changeset Guidelines
changeKind reference
- internal: Tests, CI/CD, refactoring, docs, skills — not user-facing
- fix: Bug fixes users would notice
- feature: New user-facing capabilities
- deprecation: Marking something as deprecated
- breaking: Removing or changing behavior incompatibly
- dependencies: Dependency version bumps
Message examples
internal: "Improve CI pipeline performance and test infrastructure"fix: "Fix incorrect deserialization of nullable enum properties"feature: "Add support for XML serialization in request bodies"
Package names
| Folder | Package Name |
|---|---|
http-client-python |
@typespec/http-client-python |
http-client-csharp |
@typespec/http-client-csharp |
http-client-java |
@typespec/http-client-java |
04 同仓库更多 Skills
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.
triaging-security-reports
Use when a vulnerability or security report arrives for triage, when assessing a CVE/RCE/OGNL/injection 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.
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.
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.
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 / 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.
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.