5.1K skills · sorted by relevance
Maintain vision, user journeys, evolving requirements and roadmap outcomes when intent or acceptance changes.
The English summary is being prepared. Showing the original description.
Promotes @rhinestone/sdk v3 from main to release and publishes it to npm @latest. Use when a main → release "Release" PR is open, a changeset has to reach @latest, or a release PR is stuck BEHIND or unapproved.
The English summary is being prepared. Showing the original description.
Run and configure oxlint — the high-performance JavaScript/TypeScript linter built on the Oxc compiler stack. Use this skill whenever working in a project that has oxlint installed (check for `oxlint` in package.json devDependencies or an `.oxlintrc.json` / `oxlint.config.ts` config file). This includes when you need to lint code after making changes, fix linting errors, configure oxlint rules/plugins, set up or modify `.oxlintrc.json`, or migrate from ESLint.
The English summary is being prepared. Showing the original description.
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
The English summary is being prepared. Showing the original description.
Review all uncommitted work and commits not yet pushed on the current branch, fix credible findings, commit remaining changes, and push. Use when the user invokes `$push` or asks to review, commit, and push all current branch work.
The English summary is being prepared. Showing the original description.
Audit code changes on the current branch and update docs/ + .claude/rules/ to stay in sync. Run before /pr.
The English summary is being prepared. Showing the original description.
Rebuild the pgvector gold index after source data changes. Invoke manually — replaces each collection, do NOT trigger automatically.
The English summary is being prepared. Showing the original description.
Review changed code for YAGNI, removable over-complexity, reuse, code quality, and efficiency, then apply worthwhile simplifications. Use when the user asks to simplify, clean up, tighten, de-hack recent changes, identify logic that can be dropped, or review whether added safeguards and edge-case handling are actually needed.
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.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
The English summary is being prepared. Showing the original description.
Generate a conventional commit message for the current staged git changes. Use when the user wants to commit, asks for a commit message, or asks what to write for a commit.
The English summary is being prepared. Showing the original description.
Review code against a standard checklist covering security, correctness, performance, and readability. Use when asked to review code, check a PR, or audit changes.
The English summary is being prepared. Showing the original description.
Apply code formatting rules after file edits in the source directory. Use when asked to format code or after making changes to source files.
The English summary is being prepared. Showing the original description.
Stage all changes and create a conventional commit with a generated message. Use when ready to commit and want automated staging and commit message generation.
The English summary is being prepared. Showing the original description.
Analyze the current uncommitted diff and give a detailed summary with risk assessment. Use when asking what changed, reviewing changes before a commit, or requesting a change summary.
The English summary is being prepared. Showing the original description.
Research the codebase to answer a question without making any changes. Use when exploring code, understanding architecture, or investigating how something works.
The English summary is being prepared. Showing the original description.
Identify and add new AnimeGameData field deobfuscation mappings by comparing cleartext and obfuscated AGD revisions. Use when a new Genshin Impact build changes obfuscated JSON field names or when rust/istaroth-agd-regen/src/deob.rs needs a new version mapping block.
The English summary is being prepared. Showing the original description.
Deep code review - Elixir idioms, OTP patterns, tech debt, safety. Launches 3 parallel reviewers + plan-reviewer gate. Use when: review, review this, code review, check this code, review my changes, is this good, what do you think, techdebt, tech debt, code smells.
The English summary is being prepared. Showing the original description.
[Workflow] Implement behavior already captured in a canonical spec or test-case set, with scope held, reviewed changes and verified tests. Spec gaps use workflow-feature.
The English summary is being prepared. Showing the original description.
[Utilities] Use when asking about or configuring the .claude/.codex/.agents/.opencode skills framework: command discovery/help, runtime modes, scoped settings, commit reviews, hooks, workflows or skill visibility. Explains options; changes only requested settings.
The English summary is being prepared. Showing the original description.
[Code Quality] Use when evaluating received review feedback, reviewing named code on request, or verifying a completion claim. Current diffs: changes-review; rationale: why-review.
The English summary is being prepared. Showing the original description.
[Testing] Use when generating a demo video from E2E screenshots for current changes, a commit, pull request or named user journey, covering every relevant case.
The English summary is being prepared. Showing the original description.
[Documentation] Use when a workflow step or the user asks for documentation sync after code/spec/test changes (--mode=update), or explicit reference-doc initialization and reconciliation (--mode=init).
The English summary is being prepared. Showing the original description.
Use when a diff needs a readability review — naming, single-responsibility, DRY, dead code, mismatch with codebase conventions — dispatched by /review-changes, /do-and-judge, /judge.
The English summary is being prepared. Showing the original description.