菜单
Generates pull request description body in raw markdown using the ODE PR template. Use when the user asks for a PR description, types "/pr description" or "pr description", or wants copyable markdown for a PR body. Output is always in a fenced markdown code block for one-click copy.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guides publishing and managing ODE app bundles with the Synkronus CLI (synk): config, auth, upload, versions. Use when deploying custom app zips or automating bundle uploads. Official reference is opendataensemble.org and OpenDataEnsemble/ode docs.
Helps validate ODE custom app form definitions (JSON Schema draft-07 + UI schema) and CI integration. Use when the user asks to validate forms, add validate-forms scripts, or check schema/ui consistency for Synkronus bundles. Prefer official docs at opendataensemble.org and the custom-app template repo on GitHub.
Guides adding ODE custom JSON Forms extensions (custom renderers, testers, ext.json, dynamic functions). Use when extending forms with non-standard controls or wiring extension manifests. Official behavior is documented on opendataensemble.org.
| name | pr-description |
| description | Generates pull request description body in raw markdown using the ODE PR template. Use when the user asks for a PR description, types "/pr description" or "pr description", or wants copyable markdown for a PR body. Output is always in a fenced markdown code block for one-click copy. |
Apply this skill when the user:
Infer scope from the conversation or recent edits (e.g. which files changed, what type of change).
Generate the PR body using the ODE template below. Fill in Description, Type of Change, Component(s) Affected, Related Issue(s), Testing, Breaking Changes, Documentation, and Checklist based on context. Use [x] for checked items and [ ] for unchecked.
Output only raw markdown inside a single fenced code block (language markdown) so the user can copy it. The first line inside the fence should be ## Description (or the first section heading)—no extra blank line before it.
Do not put a "# Pull Request Title" or title line in the body. Remind the user in one short sentence: The PR title is set when you create the PR (e.g. in GitHub/GitLab); use Conventional Commits, e.g. feat(docs): add X.
Use this structure. Replace placeholders and check the right boxes.
## Description
<!-- Provide a clear description of what changed and why -->
## Type of Change
- [ ] Bug Fix
- [ ] New Feature / Enhancement
- [ ] Refactor / Code Cleanup
- [ ] Documentation Update
- [ ] Maintenance / Chore
- [ ] Other (please specify):
---
## Component(s) Affected
- [ ] **formulus** (React Native mobile app)
- [ ] **formulus-formplayer** (React web app)
- [ ] **synkronus** (Go backend server)
- [ ] **synkronus-cli** (Command-line utility)
- [ ] **Documentation**
- [ ] **DevOps / CI/CD**
- [ ] **Other:** <!-- Please specify -->
---
## Related Issue(s)
<!-- Use keywords: Closes #123, Fixes #456, Resolves #789 -->
**Closes/Fixes/Resolves:** <!-- e.g., Closes #123 -->
---
## Testing
- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manually tested
- [ ] Tested on multiple platforms (if applicable)
- [ ] Not applicable
---
## Breaking Changes
- [ ] This PR introduces breaking changes
- [ ] This PR does NOT introduce breaking changes
**If breaking changes, please describe migration steps:**
---
## Documentation Updates
- [ ] Documentation has been updated
- [ ] Documentation update is not required
---
## Checklist
- [ ] Code follows project style guidelines
- [ ] All existing tests pass
- [ ] New tests added for new functionality
- [ ] PR title follows Conventional Commits format
---
**Thank you for contributing to Open Data Ensemble (ODE)!**
Always wrap the generated PR body in a single code block with language markdown so the user can copy the entire block and paste it into the PR description field. Do not add a heading above the code block like "Here's your PR body"—either output only the code block or one brief line before it (e.g. "Copy the markdown below into your PR description.").