Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

pr-description

Étoiles3

Forks1

Mis à jour1 mai 2026 à 22:05

Write the PR body — Why / What / Risk / Test plan. Skip pleasantries. Link issue. Tag CHANGELOG entry. Use 'gh pr create --body' with HEREDOC. Use when the user asks to open a PR, create a pull request, or write a PR description.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

PlugFox

PlugFox/vixen-rs

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	pr-description
description	Write the PR body — Why / What / Risk / Test plan. Skip pleasantries. Link issue. Tag CHANGELOG entry. Use 'gh pr create --body' with HEREDOC. Use when the user asks to open a PR, create a pull request, or write a PR description.

PR Description (Vixen)

Source: foxic + standard PR practice.

Title

Conventional Commits format. Under 70 chars. The body has details, not the title.

feat(captcha): add picture-pick mode
fix(spam): close timing window in dedup cache
refactor(api): extract auth middleware
docs(server): document chat config transactional write

Scopes: server, api, db, auth, bot, captcha, spam, jobs, reports, config, website, ui, i18n, docker, ci, deps.

Body sections (in this order)

Why (1-3 sentences): the problem this solves; link to issue if any (Closes #42).
What (3-7 bullets): the changes, in user-facing language. Not "renamed foo to bar" — "rename callback type for clarity."
Risk: what can break? Backwards-compat? Migration order? Performance impact? "None known" is acceptable when true.
Test plan: what was verified locally; what reviewer should re-check. Concrete commands and steps, not "tested it."
CHANGELOG: confirm [Unreleased] was updated with (component) tag, or note "internal-only, no CHANGELOG entry."

Skip

"This PR..." preamble. Start with content, not metadata.
Emoji in titles unless explicitly requested.
"Generated with Claude Code" footers in PR bodies (commits are fine; the PR description is for humans).
Restating the diff line-by-line. Reviewers can read.

gh CLI pattern

Use HEREDOC for body — preserves Markdown formatting and avoids shell quoting hell.

gh pr create --title "feat(captcha): add picture-pick mode" --body "$(cat <<'EOF'
## Why

Some users find digit captchas frustrating; picture-pick lowers friction for legit users while keeping the spam-bot solve rate similar. Closes #87.

## What

- New `ChallengeKind::PicturePick` variant + asset set under `server/assets/captcha/picture/v1/`.
- Solver UI in the callback handler (single `pick_*` action with index).
- `chat_config.captcha_kind` column; defaults to `digits`; opt-in per chat via `PATCH /chats/{id}/config`.
- Admin dashboard toggle.

## Risk

- In-flight digit challenges unaffected — `ChallengeKind` discriminates on solve.
- New assets are immutable — never overwriting existing files; v1 path is new.
- Migration is additive with default; safe to deploy app before app uses the column.

## Test plan

- `cargo test captcha::picture_pick` — green.
- `cargo sqlx prepare --check` — green.
- Manual TG bot test in dev chat — works on iOS, Android, web client.
- Admin toggle round-trips through API — verified in browser.

CHANGELOG: entry added under `[Unreleased]` `Added` `(server)` and `(website)`.
EOF
)"

Linking issues

Closes #42 / Fixes #42 in the body auto-closes on merge. Put it in Why, not the title.
Cross-repo: Closes plugfox/related-repo#42.
"Related to #N" if the PR touches but doesn't fully resolve another issue.

After opening

Return the PR URL to the user.
Don't auto-merge. Let the user (or CI gates) decide.
If review comments require non-trivial changes, run plan-before-code again before pushing.

commit-message — Conventional Commits scope reference.
verifiable-goal — populates the Test Plan section.
change-impact-assessment — populates the What / Risk sections.

Plus depuis ce dépôt

même dépôt

bump-version

PlugFox/vixen-rs

Bump the patch version in server/Cargo.toml or website/package.json after completing a major change. Use when the user asks to bump/release a version, or when CLAUDE.md's rule about version bumps after major changes applies.

2026-05-013

change-impact-assessment

PlugFox/vixen-rs

Before a non-trivial change, list affected systems — DB schema, API contract, Telegram handlers, jobs, TS types, docs. Catch ripple effects upfront, not after CI fails. Use when planning a feature, migration, refactor, or any cross-module touch.

2026-05-013

code-review-self

PlugFox/vixen-rs

Self-review before push — read the diff as a reader, scan for vixen footguns (token leaks, PII, idempotency, captcha asset overwrites), run validation pipeline, no surprise files. Use before "git push", before opening a PR, or when the user says "ready to commit".

2026-05-013

commit-message

PlugFox/vixen-rs

Write a git commit message for vixen-rs following the project's Conventional Commits convention. Use when the user asks to commit, create a commit, or write a commit message.

2026-05-013

debug-systematically

PlugFox/vixen-rs

Reproduce → bisect → root cause → fix → verify. Don't speculate, don't "add more error handling" as a guess. Use when something is broken, when a test fails intermittently, when the user says "this isn't working" or "investigate why".

2026-05-013

docker-multi-stage

PlugFox/vixen-rs

Write small, fast, reproducible Dockerfiles for the vixen-rs server (Rust) and website (bun) using multi-stage builds, cache mounts, distroless/alpine runtime images, and non-root users. Use when editing server/Dockerfile, website/Dockerfile, docker-compose.yml, or when the user asks to shrink an image or speed up a Docker build.

2026-05-013

PR Description (Vixen)

Source: foxic + standard PR practice.

Title

Conventional Commits format. Under 70 chars. The body has details, not the title.

feat(captcha): add picture-pick mode

fix(spam): close timing window in dedup cache

refactor(api): extract auth middleware

docs(server): document chat config transactional write

Scopes: server, api, db, auth, bot, captcha, spam, jobs, reports, config, website, ui, i18n, docker, ci, deps.

Body sections (in this order)

Why (1-3 sentences): the problem this solves; link to issue if any (Closes #42).

What (3-7 bullets): the changes, in user-facing language. Not "renamed foo to bar" — "rename callback type for clarity."

Risk: what can break? Backwards-compat? Migration order? Performance impact? "None known" is acceptable when true.

Test plan: what was verified locally; what reviewer should re-check. Concrete commands and steps, not "tested it."

CHANGELOG: confirm [Unreleased] was updated with (component) tag, or note "internal-only, no CHANGELOG entry."

Skip

"This PR..." preamble. Start with content, not metadata.

Emoji in titles unless explicitly requested.

"Generated with Claude Code" footers in PR bodies (commits are fine; the PR description is for humans).

Restating the diff line-by-line. Reviewers can read.

gh CLI pattern

Use HEREDOC for body — preserves Markdown formatting and avoids shell quoting hell.

gh pr create --title "feat(captcha): add picture-pick mode" --body "$(cat <<'EOF' ## Why Some users find digit captchas frustrating; picture-pick lowers friction for legit users while keeping the spam-bot solve rate similar. Closes #87. ## What - New `ChallengeKind::PicturePick` variant + asset set under `server/assets/captcha/picture/v1/`. - Solver UI in the callback handler (single `pick_*` action with index). - `chat_config.captcha_kind` column; defaults to `digits`; opt-in per chat via `PATCH /chats/{id}/config`. - Admin dashboard toggle. ## Risk - In-flight digit challenges unaffected — `ChallengeKind` discriminates on solve. - New assets are immutable — never overwriting existing files; v1 path is new. - Migration is additive with default; safe to deploy app before app uses the column. ## Test plan - `cargo test captcha::picture_pick` — green. - `cargo sqlx prepare --check` — green. - Manual TG bot test in dev chat — works on iOS, Android, web client. - Admin toggle round-trips through API — verified in browser. CHANGELOG: entry added under `[Unreleased]` `Added` `(server)` and `(website)`. EOF )"

Linking issues

Closes #42 / Fixes #42 in the body auto-closes on merge. Put it in Why, not the title.

Cross-repo: Closes plugfox/related-repo#42.

"Related to #N" if the PR touches but doesn't fully resolve another issue.

After opening

Return the PR URL to the user.

Don't auto-merge. Let the user (or CI gates) decide.

If review comments require non-trivial changes, run plan-before-code again before pushing.

commit-message — Conventional Commits scope reference.

verifiable-goal — populates the Test Plan section.

change-impact-assessment — populates the What / Risk sections.