[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACDASAHBX4RK9JQPPHJQ95":3,"skill-same:01M6ACDASAHBX4RK9JQPPHJQ95":82},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6ACDASAHBX4RK9JQPPHJQ95","seatunnel-pr-submit",null,"Draft or submit Apache SeaTunnel pull requests in English using the repository's required title and body conventions. Use when Codex needs to prepare a PR from the current branch or diff, infer a compliant `[Type][Module][SubModule] Description` title, fill the required PR template, describe what changed from git history or file diffs, or open the PR after the user provides or omits the change summary.","apache\u002Fseatunnel","apache","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4","01M6AC83E6K4FDKK7HZ8WNMQKE","The Apache Software Foundation","01M6ACD7F18WKGBBAAMFNATJ23",9805,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fapache\u002Fseatunnel\u002Fblob\u002Fdev\u002F.skills\u002Fseatunnel-pr-submit\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,9,34,35,36,37,38,39],"pr","submit","pr submit","seatunnel pr submit","open","when","describe","body","title","english","infer","branch","template","diffs","repository","pull","git","prepare","change","pull requests","codex","2026-11-10 10:12:30",false,"---\nname: seatunnel-pr-submit\ndescription: Draft or submit Apache SeaTunnel pull requests in English using the repository's required title and body conventions. Use when Codex needs to prepare a PR from the current branch or diff, infer a compliant `[Type][Module][SubModule] Description` title, fill the required PR template, describe what changed from git history or file diffs, or open the PR after the user provides or omits the change summary.\n---\n\n# SeaTunnel PR Submit\n\n## Overview\n\nDraft SeaTunnel PR titles and bodies that match the repository rules.\nPrefer the user's own summary of the change, then use the current branch diff to verify or complete it.\n\n## Workflow\n\n### 1. Collect PR context\n\nInspect the current change set before writing anything.\nPrefer committed branch changes when the branch is already ahead of its base.\nIf the user is preparing a PR before committing, inspect staged and unstaged changes and say that the draft reflects the working tree.\nRead the repository's current PR template before drafting the body so the generated content follows the latest sections and checklist wording.\n\nUse non-interactive git commands such as:\n\n```bash\ngit branch --show-current\ngit status --short\ngit diff --stat\ngit diff --name-only\ngit diff --cached --stat\ngit log --oneline -5\nsed -n '1,220p' .github\u002FPULL_REQUEST_TEMPLATE.md\n```\n\nIf an upstream branch exists, also inspect the branch-level change set:\n\n```bash\ngit log --oneline @{upstream}..HEAD\ngit diff --stat @{upstream}...HEAD\ngit diff --name-only @{upstream}...HEAD\n```\n\n### 2. Prefer the user's summary\n\nUse the user's description as the primary explanation of intent.\nUse the diff only to sharpen wording, identify the correct module, and catch obvious mismatches.\nIf the user's summary materially conflicts with the diff, pause and call out the mismatch before submitting the PR.\n\n### 3. Infer the PR title\n\nWrite the title in English.\nUse one of these formats:\n\n- `[Type][Module] Description`\n- `[Type][Module][SubModule] Description`\n\nChoose `Type` from the dominant change:\n\n| Signal | Type |\n| --- | --- |\n| New behavior, new option, new capability | `Feature` |\n| Bug fix or correction | `Fix` |\n| Optimization, cleanup, or non-breaking refinement | `Improve` |\n| Urgent CI, dependency, or release blocker fix | `Hotfix` |\n| Documentation-only change | `Docs` |\n| Test-only change | `Test` |\n| Build, tooling, or maintenance work | `Chore` |\n\nChoose `Module` from the dominant path:\n\n| Path pattern | Module | SubModule hint |\n| --- | --- | --- |\n| `seatunnel-connectors-v2\u002F...` | `Connector-V2` | Connector name |\n| `seatunnel-transforms-v2\u002F...` | `Transform-V2` | Transform name |\n| `seatunnel-engine\u002F...` | `Zeta` | Engine area if clear |\n| `seatunnel-core\u002F...` | `Core` | Omit when not needed |\n| `seatunnel-api\u002F...` | `API` | Omit when not needed |\n| `seatunnel-e2e\u002F...` | `E2E` | Suite or connector name |\n| `.github\u002F...`, CI workflow files | `CI` | Workflow or job name |\n| `bin\u002F...`, shell scripts | `Shell` | Script name |\n| `tools\u002F...` | `Tools` | Tool name |\n| `docs\u002F...` only | `Docs` | Usually omit submodule |\n\nApply these rules:\n\n- Prefer a single dominant module instead of listing every touched area.\n- Add `SubModule` only when one connector, transform, or area clearly dominates the diff.\n- Keep the description concise and action-oriented.\n- Describe the actual change, not the development process.\n- Do not add Chinese text to the title.\n\nExamples:\n\n- `[Fix][Connector-V2][Milvus] Fix partition creation`\n- `[Feature][Transform-V2] Support AES_GCM algorithm in FieldEncrypt`\n- `[Improve][Zeta] Optimize multiple table job config parsing`\n- `[Docs] Remove redundant lines from transform docs`\n\n### 4. Write the PR body\n\nMirror the current `.github\u002FPULL_REQUEST_TEMPLATE.md` headings and checklist structure, and keep the body in English.\nUse the repository template as the source of truth when wording changes in the future.\nAt minimum, include these sections:\n\n```md\n### Purpose of this pull request\n\u003CExplain what changed and why. Prefer 1 short paragraph or 2 flat bullets. Mention the real files, modules, or behaviors changed.>\n\n### Does this PR introduce _any_ user-facing change?\n\u003CWrite the behavior difference if users can notice it. For docs-only or internal-only changes, write `No`.>\n\n### How was this patch tested?\n\u003CList the real verification that ran. Never claim tests that did not run. If nothing ran yet, write `Not run yet.`>\n\n### Check list\n- [ ] New dependency is documented under the New License Guide\n- [ ] Documentation is updated if needed\n- [ ] incompatible-changes.md is updated if needed\n- [ ] Connector changes include plugin-mapping.properties, seatunnel-dist pom, CI label, E2E, and plugin_config updates if needed\n```\n\nWrite the body from evidence:\n\n- Mention the exact scope of the diff instead of generic phrases.\n- If the user already summarized the change, use that wording as the backbone of the first section.\n- If the user gave no summary, infer the purpose from changed files, removed or added lines, and recent commits.\n- For docs-only changes, explain which docs were updated and what was corrected or removed.\n- Keep the same checklist intent as the repository template even if individual links or wording have changed.\n- Leave checklist items unchecked by default unless the current evidence clearly supports checking them.\n\n### 5. Handle testing honestly\n\nBefore claiming a PR is ready, prefer repository validation that matches the actual scope.\nFor SeaTunnel work, the common baseline is:\n\n```bash\n.\u002Fmvnw spotless:apply\n.\u002Fmvnw -q -DskipTests verify\n.\u002Fmvnw test\n```\n\nUse narrower verification when the change is local and the user prefers a smaller check, but never invent coverage.\nIf validation has not happened yet, say so directly in the PR body and recommend the relevant command before opening the PR.\n\n### 6. Submit the PR when asked\n\nIf the user asks to open the PR, prepare the final title and body first, then create the PR with a non-interactive flow.\nPrefer the available GitHub integration.\nIf you fall back to `gh`, use a non-interactive command such as `gh pr create --title ... --body-file ...`.\n\nKeep these constraints:\n\n- Follow the repository title format exactly.\n- Keep the PR body in English.\n- Describe only the current branch change set.\n- Do not mention other assistants or tool brands in the PR title or body.\n- Do not claim tests, docs, or compatibility work that did not happen.\n\n## Output Format\n\nWhen the user asks for a draft, return:\n\n```md\nTitle: [Type][Module][SubModule] Description\n\nBody:\n### Purpose of this pull request\n...\n\n### Does this PR introduce _any_ user-facing change?\n...\n\n### How was this patch tested?\n...\n\n### Check list\n- [ ] ...\n```\n\nWhen the user also gives a manual summary, integrate it first and only use the diff to refine the title and fill in missing facts.\n","# SeaTunnel PR Submit\n\n## Overview\n\nDraft SeaTunnel PR titles and bodies that match the repository rules.\nPrefer the user's own summary of the change, then use the current branch diff to verify or complete it.\n\n## Workflow\n\n### 1. Collect PR context\n\nInspect the current change set before writing anything.\nPrefer committed branch changes when the branch is already ahead of its base.\nIf the user is preparing a PR before committing, inspect staged and unstaged changes and say that the draft reflects the working tree.\nRead the repository's current PR template before drafting the body so the generated content follows the latest sections and checklist wording.\n\nUse non-interactive git commands such as:\n\n```bash\ngit branch --show-current\ngit status --short\ngit diff --stat\ngit diff --name-only\ngit diff --cached --stat\ngit log --oneline -5\nsed -n '1,220p' .github\u002FPULL_REQUEST_TEMPLATE.md\n```\n\nIf an upstream branch exists, also inspect the branch-level change set:\n\n```bash\ngit log --oneline @{upstream}..HEAD\ngit diff --stat @{upstream}...HEAD\ngit diff --name-only @{upstream}...HEAD\n```\n\n### 2. Prefer the user's summary\n\nUse the user's description as the primary explanation of intent.\nUse the diff only to sharpen wording, identify the correct module, and catch obvious mismatches.\nIf the user's summary materially conflicts with the diff, pause and call out the mismatch before submitting the PR.\n\n### 3. Infer the PR title\n\nWrite the title in English.\nUse one of these formats:\n\n- `[Type][Module] Description`\n- `[Type][Module][SubModule] Description`\n\nChoose `Type` from the dominant change:\n\n| Signal | Type |\n| --- | --- |\n| New behavior, new option, new capability | `Feature` |\n| Bug fix or correction | `Fix` |\n| Optimization, cleanup, or non-breaking refinement | `Improve` |\n| Urgent CI, dependency, or release blocker fix | `Hotfix` |\n| Documentation-only change | `Docs` |\n| Test-only change | `Test` |\n| Build, tooling, or maintenance work | `Chore` |\n\nChoose `Module` from the dominant path:\n\n| Path pattern | Module | SubModule hint |\n| --- | --- | --- |\n| `seatunnel-connectors-v2\u002F...` | `Connector-V2` | Connector name |\n| `seatunnel-transforms-v2\u002F...` | `Transform-V2` | Transform name |\n| `seatunnel-engine\u002F...` | `Zeta` | Engine area if clear |\n| `seatunnel-core\u002F...` | `Core` | Omit when not needed |\n| `seatunnel-api\u002F...` | `API` | Omit when not needed |\n| `seatunnel-e2e\u002F...` | `E2E` | Suite or connector name |\n| `.github\u002F...`, CI workflow files | `CI` | Workflow or job name |\n| `bin\u002F...`, shell scripts | `Shell` | Script name |\n| `tools\u002F...` | `Tools` | Tool name |\n| `docs\u002F...` only | `Docs` | Usually omit submodule |\n\nApply these rules:\n\n- Prefer a single dominant module instead of listing every touched area.\n- Add `SubModule` only when one connector, transform, or area clearly dominates the diff.\n- Keep the description concise and action-oriented.\n- Describe the actual change, not the development process.\n- Do not add Chinese text to the title.\n\nExamples:\n\n- `[Fix][Connector-V2][Milvus] Fix partition creation`\n- `[Feature][Transform-V2] Support AES_GCM algorithm in FieldEncrypt`\n- `[Improve][Zeta] Optimize multiple table job config parsing`\n- `[Docs] Remove redundant lines from transform docs`\n\n### 4. Write the PR body\n\nMirror the current `.github\u002FPULL_REQUEST_TEMPLATE.md` headings and checklist structure, and keep the body in English.\nUse the repository template as the source of truth when wording changes in the future.\nAt minimum, include these sections:\n\n```md\n### Purpose of this pull request\n\u003CExplain what changed and why. Prefer 1 short paragraph or 2 flat bullets. Mention the real files, modules, or behaviors changed.>\n\n### Does this PR introduce _any_ user-facing change?\n\u003CWrite the behavior difference if users can notice it. For docs-only or internal-only changes, write `No`.>\n\n### How was this patch tested?\n\u003CList the real verification that ran. Never claim tests that did not run. If nothing ran yet, write `Not run yet.`>\n\n### Check list\n- [ ] New dependency is documented under the New License Guide\n- [ ] Documentation is updated if needed\n- [ ] incompatible-changes.md is updated if needed\n- [ ] Connector changes include plugin-mapping.properties, seatunnel-dist pom, CI label, E2E, and plugin_config updates if needed\n```\n\nWrite the body from evidence:\n\n- Mention the exact scope of the diff instead of generic phrases.\n- If the user already summarized the change, use that wording as the backbone of the first section.\n- If the user gave no summary, infer the purpose from changed files, removed or added lines, and recent commits.\n- For docs-only changes, explain which docs were updated and what was corrected or removed.\n- Keep the same checklist intent as the repository template even if individual links or wording have changed.\n- Leave checklist items unchecked by default unless the current evidence clearly supports checking them.\n\n### 5. Handle testing honestly\n\nBefore claiming a PR is ready, prefer repository validation that matches the actual scope.\nFor SeaTunnel work, the common baseline is:\n\n```bash\n.\u002Fmvnw spotless:apply\n.\u002Fmvnw -q -DskipTests verify\n.\u002Fmvnw test\n```\n\nUse narrower verification when the change is local and the user prefers a smaller check, but never invent coverage.\nIf validation has not happened yet, say so directly in the PR body and recommend the relevant command before opening the PR.\n\n### 6. Submit the PR when asked\n\nIf the user asks to open the PR, prepare the final title and body first, then create the PR with a non-interactive flow.\nPrefer the available GitHub integration.\nIf you fall back to `gh`, use a non-interactive command such as `gh pr create --title ... --body-file ...`.\n\nKeep these constraints:\n\n- Follow the repository title format exactly.\n- Keep the PR body in English.\n- Describe only the current branch change set.\n- Do not mention other assistants or tool brands in the PR title or body.\n- Do not claim tests, docs, or compatibility work that did not happen.\n\n## Output Format\n\nWhen the user asks for a draft, return:\n\n```md\nTitle: [Type][Module][SubModule] Description\n\nBody:\n### Purpose of this pull request\n...\n\n### Does this PR introduce _any_ user-facing change?\n...\n\n### How was this patch tested?\n...\n\n### Check list\n- [ ] ...\n```\n\nWhen the user also gives a manual summary, integrate it first and only use the diff to refine the title and fill in missing facts.\n",{"name":5,"description":7},"dev","fcb404cd947da03a712c4ae9ee9068744bd946a5",".skills\u002Fseatunnel-pr-submit",2466,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fseatunnel","https:\u002F\u002Fseatunnel.apache.org\u002F","https:\u002F\u002Fgithub.com\u002Fapache","https:\u002F\u002Fwww.apache.org\u002F","2026-11-14 18:13:47",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add apache\u002Fseatunnel --skill seatunnel-pr-submit",{"tool":60,"command":61},"bunx","bunx skills add apache\u002Fseatunnel --skill seatunnel-pr-submit",{"tool":63,"command":64},"pnpm","pnpm dlx skills add apache\u002Fseatunnel --skill seatunnel-pr-submit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Fseatunnel\u002Fblob\u002Fdev\u002F.skills\u002Fseatunnel-pr-submit\u002FSKILL.md",true,[68,74,78],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"agents\u002Fopenai.yaml","REFERENCE","参考文档",1009,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fseatunnel\u002Fblob\u002Fdev\u002F.skills\u002Fseatunnel-pr-submit\u002Fagents\u002Fopenai.yaml",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fexamples.md",12437,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fnoob-mode\u002Freferences\u002Fexamples.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fglossary.md",21585,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fnoob-mode\u002Freferences\u002Fglossary.md",[83],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":94,"publishedAt":40},"01M6ACDEEZV2HYP1FHPCM20NTM","seatunnel-test-suite","Write or review Apache SeaTunnel E2E (Testcontainers) and unit tests so they are stable, leak-free, and deterministic. Use when creating a new *IT\u002F*Test class, reviewing a test diff, or refactoring a flaky or leaking test.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fseatunnel\u002Fblob\u002Fdev\u002F.skills\u002Fseatunnel-test-suite\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[95,96,97,98,9,99,100,101,102,103,104,105,106,107,108,109,110,111,24,112],"test","suite","test suite","seatunnel test suite","e2e","refactoring","write","use","diff","unit tests","deterministic","tests","free","unit","it","testcontainers","review","new"]