القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
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.
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.
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".
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.
استنادا إلى تصنيف SOC المهني
| name | commit-message |
| description | 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. |
Follow Conventional Commits with the scopes used in this repo.
<type>(<scope>): <subject>
<body — optional, wraps at 72 chars>
feat, fix, refactor, docs, chore, test, perf, style, build, ci.
server, api, db, auth, bot, captcha, spam, jobs, reports, config, moderation.website, ui, auth, chats, moderation, reports, settings, i18n.docker, ci, deps.feat(captcha): add digit-pad refresh button.! after scope (feat(api)!: ...) and a BREAKING CHANGE: footer.! after scope: feat(api)!: rename /chats/list to /chats/index.BREAKING CHANGE: footer paragraph explaining the migration path.bump-version skill.git status / git diff --staged — make sure only relevant files are staged..env*, .secrets/, secrets, node_modules/, or target/ artifacts.initData payload — git diff --staged | grep -i 'bot[0-9]\+:' and grep -i 'auth_date=' should both be empty.server/ or website/, the user should have run the corresponding /server-check or /website-check first. If they haven't and the change is non-trivial, mention it before committing.server/migrations/ and .sqlx/ is not staged, that's almost certainly a mistake — flag it.Only add Co-Authored-By: Claude ... when the user has explicitly asked you to make the commit. Do not add it for commits written by the user themselves.
Co-Authored-By: ... ONLY when the user explicitly asks for the commit. Don't preempt — silent author injection is noise.