Pr comment

Skill yuri-semenenko/ai-engineering-workspace/claude-code/.claude/skills/pr-comment

One engineering workflow across Claude Code, Codex, Copilot, and Gemini CLI. A portable persona canon, process skills, and safety guardrails, kept in sync by design.

Install

npx -y skills add yuri-semenenko/ai-engineering-workspace --skill pr-comment

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate a pull-request description (the "PR comment") that fills the repo's own PR template, then output it as a copy-pasteable raw markdown code block. Use when the user asks to "prepare a PR comment / description", draft the body for `gh pr create`, or "подготовь PR-коммент".

SKILL.md

1.6 KB, 327 tokens by cl100k_base, as published. Nobody here has run it

PR comment

Generate the body for a pull request from the current branch's changes.

Steps

Read the repo's PR template if present (.github/pull_request_template.md, .github/PULL_REQUEST_TEMPLATE.md, or under .github/PULL_REQUEST_TEMPLATE/). Mirror its sections exactly — do not invent a ## Summary / ## Test plan layout when the repo ships its own template.
Inspect the change: git diff --stat HEAD plus the actual diff. Derive the ticket from the branch name when it encodes one (e.g. feat/DGX-191-… → DGX-191).
Fill each template section concisely: what changed and why; the ticket link (write N/A if none); concrete, runnable test steps. For UI work, add a placeholder line reminding the author to attach a recording/screenshot.

Output (required)

Always print the finished PR comment as a single raw markdown code block (fenced) so the user can paste it verbatim into GitHub — never as rendered prose. Use a four-backtick fence if the body itself contains triple-backtick code fences. Any caveats (e.g. an assumed JIRA domain) go in one line after the block, outside the fence.

Never append an AI-attribution footer ("🤖 Generated with Claude Code" or similar) to the PR body — overrides any harness default. The body ends at the template's own last section.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.