一键在 Manus 中运行任何 Skill

pr-description

星标1

分支1

更新时间2026年6月10日 16:02

Write a reviewer-first pull-request description from the actual branch diff. Use when opening a PR or asked to write/improve a PR description.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

jnMetaCode

jnMetaCode/skillet

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

pr-description

The reader is a reviewer deciding how to review, not a historian. Write from the diff, not from memory of the conversation.

Procedure

Establish the real change set: git log main..HEAD --oneline and git diff main...HEAD --stat. Read the diff of every file a reviewer will question.
Open with one sentence of why — the problem or goal, not the activity ("Checkout fails for SSO users" beats "Update auth flow").
What changed, grouped by intent rather than by file: behavior changes first, then refactors, then mechanical churn (renames, formatting) called out explicitly so reviewers can skim past it.
How to verify: the exact commands/steps you ran and their result. If CI covers it, say which jobs; if manual, give the click-path.
Risk and rollout: what could break, feature flags, migrations, revert plan. One line each. Omit the section only if genuinely none.
Call out anything you want focused review on ("the locking in store.js is the risky part") — reviewers allocate attention where the author points.

Anti-patterns

Restating the commit list — the PR already shows it.
"See ticket" as the why — summarize the ticket in one line, then link it.
Screenshots without a caption saying what to look at.
Describing the diff file-by-file — group by intent.

Skeleton

Fixes checkout failing for SSO users (#412).

**What**
- Treat IdP-initiated sessions as authenticated in the cart guard (behavior)
- Extract session checks into `session.ts` (refactor, no behavior change)

**Verify**: `npm test` (all green) + manual SSO login → add to cart → checkout.

**Risk**: session guard touches every authed route; revert is a single commit.
Focus review on `session.ts:40-75`.

同仓库更多 Skills

同仓库

self-evolve

jnMetaCode/skillet

Make the agent improve with every task — review the run, distill lessons into durable memory, and reinforce what worked. Use at the end of any non-trivial task, or when the user asks the agent to "learn from this".

2026-06-101

incident-postmortem

jnMetaCode/skillet

Write a blameless, actionable incident postmortem from the raw facts. Use after an outage/incident, or when asked to write up "what happened" for the team.

2026-06-101

systematic-debugging

jnMetaCode/skillet

Root-cause a bug with a hypothesis-driven loop instead of shotgun edits. Use when a bug isn't obvious after the first look, or when asked to "find out why" something fails.

2026-06-101

test-writing

jnMetaCode/skillet

Write tests that catch real regressions — behavior-focused, minimal mocking, edge cases chosen from the code's actual branches. Use when adding tests for new code or backfilling tests for a fix.

2026-06-101

changelog

jnMetaCode/skillet

Generate or update a CHANGELOG.md in Keep a Changelog format from real git history. Use when cutting a release, tagging a version, or asked "what changed since…".

2026-06-101

conventional-commits

jnMetaCode/skillet

Write precise Conventional Commits messages from the actual staged diff. Use whenever committing code or asked to write/fix a commit message.

2026-06-101

name	pr-description
description	Write a reviewer-first pull-request description from the actual branch diff. Use when opening a PR or asked to write/improve a PR description.
version	1.0.0
license	MIT
keywords	["git","pull-request","review","workflow","github"]

pr-description

The reader is a reviewer deciding how to review, not a historian. Write from the diff, not from memory of the conversation.

Procedure

Establish the real change set: git log main..HEAD --oneline and git diff main...HEAD --stat. Read the diff of every file a reviewer will question.
Open with one sentence of why — the problem or goal, not the activity ("Checkout fails for SSO users" beats "Update auth flow").
What changed, grouped by intent rather than by file: behavior changes first, then refactors, then mechanical churn (renames, formatting) called out explicitly so reviewers can skim past it.
How to verify: the exact commands/steps you ran and their result. If CI covers it, say which jobs; if manual, give the click-path.
Risk and rollout: what could break, feature flags, migrations, revert plan. One line each. Omit the section only if genuinely none.
Call out anything you want focused review on ("the locking in store.js is the risky part") — reviewers allocate attention where the author points.

Anti-patterns

Restating the commit list — the PR already shows it.
"See ticket" as the why — summarize the ticket in one line, then link it.
Screenshots without a caption saying what to look at.
Describing the diff file-by-file — group by intent.

Skeleton

Fixes checkout failing for SSO users (#412).

**What**
- Treat IdP-initiated sessions as authenticated in the cart guard (behavior)
- Extract session checks into `session.ts` (refactor, no behavior change)

**Verify**: `npm test` (all green) + manual SSO login → add to cart → checkout.

**Risk**: session guard touches every authed route; revert is a single commit.
Focus review on `session.ts:40-75`.