← ClaudeAtlas

dsh-pr-descriptionlisted

Use when creating a deepseek-harness pull request, or when updating its description after later changes or a handled review round. Defines each description section, Issue references, test design, change-specific disclosures, and the AI Usage section with its levels, stages, grading rules, AI-DECLARATION badge, and update timing.
SOYL-AI/soyl-skills-hub · ★ 0 · AI & Automation · score 75
Install: claude install-skill SOYL-AI/soyl-skills-hub
# Writing PR descriptions This skill defines what a deepseek-harness PR description contains, how to write it, and when to update it. The [PR template](../../../.github/pull_request_template.md) supplies only the section headings and placeholders; this skill owns the requirements for each section. Every PR description follows this skill, including PRs created with `gh pr create --body-file`, which skips the template. ## Scope - Write the complete description when you create the PR. - After the PR exists, update the affected sections when the description no longer matches the PR, at times you judge suitable. - Each PR in a stack has its own description, which covers only that layer's changes against its base branch. ## Description structure The description uses four second-level headings, in this order: `## Motivation`, `## Changes`, `## Testing`, and `## AI Usage`. Write fixed section headings and labels, such as **Interface changes**, **Behavior changes**, **Test design**, and **Test entries**, in English. Write table headers and the rest of the description in the PR description's language, Chinese unless a human asked for another language. ### Motivation - State the problem in one sentence. - Reference at least one same-repository Issue: use `Fixes #N`, `Closes #N`, or `Resolves #N` when the PR resolves it, and `Refs #N` when it only gives context. PR numbers do not count as Issue references, and neither do references inside HTML comments, code fences, or inline cod