菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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".
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.
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".
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.
Evaluate a 3rd-party Claude skill before importing — source trust, duplicate check, rule extraction, vixen-fit. Reject vague triggers and off-scope content. Use when the user shares a skill URL, asks "should we adopt this skill", or proposes importing from a marketplace.
| name | change-impact-assessment |
| description | 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. |
Source: vixen monorepo + foxic patterns.
Run through this list before writing code. Each "yes" is a checkbox you owe.
#[utoipa::path]) updated?website/src/features/*/types.ts and any downstream stores?en.server/docs/*.md / website/docs/*.md is now stale? Update in the same PR..env.example + server/docs/config.md + Compose.# All Rust files referencing the changed symbol:
rg -l '<Symbol>' --type rust
# All TS files:
rg -l '<symbol>' --type ts
# All docs that mention it:
rg '<symbol>' server/docs website/docs docs
If a symbol shows up in 5 files, you have 5 places to think about.
Sunset header for one release. Then remove.Removed (or Changed with Breaking note) with migration guidance for the operator.bump-version/SKILL.md.chat_config.spam_weights shape change → every spam rule referencing the struct + serde fixtures + admin UI form.Auth extractor.moderation_actions schema → admin dashboard ledger view + public report aggregates + idempotency uniqueness key.RedactedToken cache + WebApp HMAC key derivation.website/i18n/messages/.State this before writing code:
Impact. DB: 1 migration (
add_chat_lang). API:PATCH /chats/{id}/config— new fieldlang, additive, backwards-compatible. Handlers: none. Jobs: none. TS types:ChatConfigDto.lang?: string. i18n: 1 new key (chat.config.lang.label) — needs en + ru + uk. Docs:server/docs/database.md,server/docs/api.md. Deploy: migrate first, then app (additive, safe).
Keep it tight. If the list is empty for a row, say "none" — don't omit.
plan-before-code — combine with this assessment for the planning step.code-review-self — verify each impact row was actually addressed in the diff.pr-description — the impact list maps directly to PR's "What" + "Risk" sections.