25 skills · sorted by relevance
Draft or update GitHub pull request descriptions using the actual changes and related context. Explain the problem, changed behavior, and review concerns in plain language, including breaking changes and explicit issue-closing references when applicable.
Check a pull request’s title and description against its commits and code changes. Identify missing major changes or outdated claims, propose accurate wording, and apply agreed updates while following the repository’s existing template.
Commit and push code changes, then open a pull request with a clear title and description. You can also draft or update PR descriptions and hand published requests to the follow-up monitoring workflow.
Submit current work as a GitHub pull request, handling relevant uncommitted changes and reviewing prose before pushing. After creating the PR, run companion skills to generate changelog files, update the description, and return its URL.
Calculates added and deleted lines for a pull request and maintains a three-line summary for implementation, tests, and other files. Preserves existing description text and checks the published counts against the current diff.
Draft a pull request description that explains the problem, implementation, trade-offs, and testing. It combines source-backed reasoning, validated Mermaid diagrams, and actual validation output into one Markdown file reviewers can assess on its own.
Update Han plugin documentation so every skill, agent, guidance doc, index, and cross-reference is current and accurate. On a non-default branch, scopes the pass to entities the branch actually touched. On the default branch, performs a full documentation sweep across the whole plugin. Use when updating, refreshing, syncing, auditing, or verifying Han's docs after changing skills, agents, references, or top-level guidance — including "update the docs", "doc sweep", "refresh documentation", "audit the docs", "make sure the docs are current". This is a repository-maintenance skill for the Han repo itself, not a general documentation skill — use /project-documentation to document features in arbitrary projects, /han-release to cut a release (and update CHANGELOG), and /update-pr-description for PR bodies.
The English summary is being prepared. Showing the original description.
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when releasing, cutting a release, shipping a new Han version, publishing release notes, or tagging a version. Always stops for approval before creating any tag, because a pushed tag is never moved. Requires the gh CLI, jq, the claude CLI, and a clean git checkout. This is a repository-maintenance skill for the Han repo itself, not a general review or PR skill — use code-review for local review, post-code-review-to-pr to post a PR review, and update-pr-description for PR bodies.
The English summary is being prepared. Showing the original description.
Generate a PR description from the current branch's changes against a GitHub PR, using the gh CLI. Use when writing, drafting, or updating pull request descriptions, PR summaries, or PR bodies. Does not review code or post review comments — use code-review for local review or post-code-review-to-pr for posting a review to GitHub.
The English summary is being prepared. Showing the original description.
Run a full pull request review and post review comments directly to the current branch's GitHub PR. Requires the gh CLI to be installed and a PR to already exist for the current branch. Use when you want review feedback posted to GitHub as PR comments. For local code review without posting to GitHub, use code-review instead. Does not write or update PR descriptions — use update-pr-description for that.
The English summary is being prepared. Showing the original description.
Creates and maintains project documentation for features, systems, and components. Use when documenting how a feature, system, or component works — including writing, updating, or organizing docs. Does not scan or detect the project's technology stack — use project-discovery for repository analysis and config detection. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not create or update coding standards — use coding-standard instead. Does not generate PR descriptions — use update-pr-description for that. Does not produce runbooks for operational scenarios — use runbook for that. Does not rewrite existing prose for readability — use edit-for-readability for that. Does not produce an ephemeral, understand-now overview of code or a PR — use code-overview for that.
The English summary is being prepared. Showing the original description.
Готовит заголовок и описание pull request по изменениям в ветке. Используй, когда просят описать PR, подготовить pull request или написать описание изменений.
The English summary is being prepared. Showing the original description.
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
The English summary is being prepared. Showing the original description.
Publish local Incan or Encero repository changes to GitHub using project standards. Use when the user asks to yeet, publish, commit and PR, push a branch and open a review-ready or draft PR from local changes while requiring the repo-local commit-message and PR-description conventions.
The English summary is being prepared. Showing the original description.
Generate a PR description following the repository's pull request template. Use when the user asks to create, draft, or generate a PR description for a pull request. The skill automatically locates the PR template in the target repository and fills it in based on the git diff.
The English summary is being prepared. Showing the original description.
Generate a PR description for the current branch against your base branch.
The English summary is being prepared. Showing the original description.
Write a clear pull request description. Use when the user says "write a PR description", "PR template", "pull request description", "how do I describe this change", "commit message for this", "document this change", "open a PR for", or is about to merge code and needs to communicate what changed and why - even if they don't explicitly say "PR description".
The English summary is being prepared. Showing the original description.
BE Dev (Backend Developer) agent. Reads BA + TechLead + PM artifacts and generates backend source code files, .env.example, and pr-description.md. No hardcoded credentials. Part of the Virtual Team Skill pipeline.
The English summary is being prepared. Showing the original description.
FE Dev (Frontend Developer) agent. Reads BA + TechLead + PM + BE artifacts and generates frontend source code files and pr-description.md. Part of the Virtual Team Skill pipeline.
The English summary is being prepared. Showing the original description.
Generate developer artifacts from Jira tickets via the jira-as wrapper: branch names, PR descriptions, parsed commits, commit/PR-to-issue links. Triggers: 'branch name for KEY', 'PR description for KEY', 'parse commits for issue keys', 'link PR to KEY'. NOT for executing git/gh commands directly (mk:ship); NOT for issue CRUD (mk:jira-issue).
The English summary is being prepared. Showing the original description.
Draft a pull request description from the current branch diff plus rolling-wave project context. Use when the user wants PR body text, changes, potential risks, or reviewer notes for a branch, especially after completing a rolling-wave slice. Defaults to the Git Town parent branch when no base branch is named.
The English summary is being prepared. Showing the original description.
Write a pull request description with summary, motivation, and test plan. Use when creating a PR, asked for a PR description, or preparing to submit a pull request.
The English summary is being prepared. Showing the original description.
PR のタイトルと本文を、レビューする人の問いに diff に現れない情報で答える形で書くための規範。書く手順（事実の一覧、節への割り当て、確認の突き合わせ）、節のカタログ、規模の目安、確認したことの書き方、言語の決め方、提出前チェックを定める。PR を作る・本文を書き直すとき（`gh pr create`、`gh pr edit`、`/create-pr`、会話中の「PR 出して」）に使う。commit メッセージ（`/commit` を使う）や issue 本文には使わない。
The English summary is being prepared. Showing the original description.
Review whether the PR description is review-ready and consistent with the diff (Why/What, impact, tests, linked issues).
The English summary is being prepared. Showing the original description.