0 Fork 0

Files

T

Dmitry DementievandClaude Opus 5 e0048bb5b2 feat(skills): добавлен скилл visual-pr для описания PR

- Зачем: не было скилла про содержание описания PR — только gh-команды
  в github. Формат humanlayer/visual-pr совпадает с принятой структурой
  коммитов «Зачем / Что / Проверка» и опирается на уже установленный show-me.
- Что: адаптированная копия humanlayer/skills visual-pr. Убраны привязки
  к платформе HumanLayer (.humanlayer/tasks, permalink из хука), дубль
  show-me заменён ссылкой на установленный скилл, финальный отчёт свёрнут
  в одну строку. Скилл хостинг-независимый (glab, tea, gh), ручной вызов
  через disable-model-invocation, язык описания — по истории коммитов.
  Шаблон references/pr_description_template.md — без изменений.
  В .skill-lock.json не добавлен, чтобы npx skills update не перезатёр
  правки.
- Проверка: SKILL.md вычитан по правилам writing-for-agents (кэш --help
  и дубли шаблона убраны); ссылка ../show-me/SKILL.md резолвится через
  ~/.claude/skills. Прогон на реальном PR ещё не выполнен.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-17 18:06:54 +03:00

1.7 KiB

Raw Permalink Blame History

name, description, disable-model-invocation

name	description	disable-model-invocation
visual-pr	Describe the current branch's pull request for a reviewer — one-sentence why, reviewer notes, and a show-me-style change outline.	true

Describe a Pull Request

Create or update the pull request (merge request on GitLab) for the current branch so a reviewer sees why the change exists and the shape of the implementation. Work through the hosting's CLI (glab, tea, gh); without one, hand the finished description to the user to paste.

Adapted from humanlayer/skills visual-pr.

Workflow

Identify or create the pull request:
- Check the current branch for a PR.
- If none exists, review git status --short --branch and the branch's commits; commit task-related changes when needed, push the branch with an upstream, and create the PR.
- Ask the user to select a PR only when the current branch has no relevant work and there is no safe current-branch PR to create.
Gather only the context needed to explain the change:
- Read the ticket and any relevant task artifacts.
- Read the complete PR diff and enough surrounding code to understand behavior and ownership.
- Read ../show-me/SKILL.md for the visual vocabulary used in the change outline.
Write the description by filling references/pr_description_template.md; the PR body is the filled template. Write in the language of the repository's commit history.
Publish it to the PR and confirm the update succeeded.
Report the PR URL, a 2-3 sentence summary of the change, and the changed files.

Write as one human talking to another: simple, coherent, concise language.

1.7 KiB Raw Permalink Blame History

Describe a Pull Request

Workflow

1.7 KiB

Raw Permalink Blame History