pr-description
Draft or update a pull request title and description for the current repository. Use when preparing, creating, or editing a pull request.
72
Quality
90%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Securityby
Passed
No findings from the security scan
Pull Request Description
Inspect the diff against the base branch and the included commits before writing.
Title
- Use a concise, specific, capitalized imperative.
- Describe the outcome rather than the implementation mechanism.
- Do not use Conventional Commit prefixes such as
feat:orfix:.
Body
- Explain what changed, why it changed, and its impact.
- Link related issues when they are known.
- List only validation that was actually run, including the result.
- Mention breaking changes, limitations, or important reviewer context when applicable.
Do not invent behavior, test results, or issue links. Create or edit a remote pull request only when the user explicitly asks.
- Repository
- chdb-io/chdb
- Commit
e93104d
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.