بنقرة واحدة
benchmark-advisor
Suggests which benchmarks to run based on code changes
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Suggests which benchmarks to run based on code changes
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run the pragmatic-skeptic 'ponytail' reviewer over the current diff to surface over-engineering — code, abstractions, dependencies, files, or process steps the problem does not need. Read-only and advisory; never trims safety, security, accessibility, data-loss handling, or their tests. Use before pushing a PR, when a change feels heavier than the task warranted, or when boilerplate/a new dependency crept in. Triggers: 'ponytail review', 'is this over-engineered', 'what can I delete here', 'did I over-build this'.
Use this skill to run a structured user-discovery interview for Caro and save the transcript into docs/discovery/transcripts/ under the project's anonymization rules. Use when a new product line or major feature spec needs to clear Gate 1 of .claude/rules/validation-discipline.md (the 20-transcripts rule). Also use to synthesize transcripts into the hypothesis ledger after each batch of 5 interviews. Triggers - "run a discovery interview for <feature>", "log this user conversation as a Caro discovery transcript", "synthesize this week's transcripts into the hypothesis ledger".
Safely reclaim disk space in the caro project. Cleans Rust build cache, stale git worktrees (both .claude/worktrees/ and .worktrees/), empty stubs, and node_modules using a tiered audit that preserves any worktree with uncommitted changes, missing remotes, or a lock file. Use when du shows the project > 30 GB or disk free is low.
DEPRECATED 2026-05-16 — use caro-shell instead. This skill recommends the --backend claude flag and a ~/.config/caro/config.toml path that do not work on the current caro 1.4.0 binary, and its 522-line educational body is 4× the size of caro-shell for no benefit to an agent. Will be removed after 2026-08-01.
Use this skill when the user needs a POSIX shell command synthesized from natural language — "how do I find/grep/awk/find files modified in the last hour", "kill the process on port 3000", "tar this up excluding .git", or any other terminal-task-as-prose. Shells out to the `caro` CLI for safety-validated command inference and presents the suggestion for explicit approval. Refuses to execute the command itself.
Build, render, ship, AND MAINTAIN the caro landing-page demo video using Remotion. Use when creating, updating, re-rendering, extending the project demo MP4 at website/public/caro-demo.mp4 — or when responding to a drift alert from the caro-demo-drift CI workflow or a beads task with label `caro-demo-video`.
| name | benchmark-advisor |
| description | Suggests which benchmarks to run based on code changes |
This skill analyzes your code changes and recommends specific Criterion benchmarks to run.
This skill automatically activates when:
git diff to see which files you've modifiedcargo bench commands with explanationsSimply ask:
# 1. Detect changed files
CHANGED_FILES=$(git diff --name-only HEAD)
# 2. Load mapping configuration
# See mapping.toml for file-to-benchmark mappings
# 3. Match changed files to benchmarks
# Example mappings:
# src/cache/**/*.rs → cargo bench --bench cache
# src/config/**/*.rs → cargo bench --bench config
# src/main.rs → cargo bench (full suite - affects startup time)
# 4. Generate recommendation with explanation
User: "What benchmarks should I run?"
Claude: "I analyzed your changes and found modifications to:
src/cache/manifest.rssrc/cache/lru.rsRecommended benchmarks:
cargo bench --bench cache
Why: Changes to cache implementation files can affect cache operation performance (get_model, add_model, remove_model, lru_eviction).
You can also run the full suite if you want comprehensive validation:
cargo bench
```"
## Mapping Configuration
The skill uses `mapping.toml` to define file patterns and their corresponding benchmarks:
```toml
# Cache-related files
[[mapping]]
pattern = "src/cache/**/*.rs"
benchmark = "cargo bench --bench cache"
reason = "Cache implementation changes can affect cache operation performance"
# Config-related files
[[mapping]]
pattern = "src/config/**/*.rs"
benchmark = "cargo bench --bench config"
reason = "Config loading and merging performance may be impacted"
# Main entry point
[[mapping]]
pattern = "src/main.rs"
benchmark = "cargo bench"
reason = "Main entry point affects startup time - run full suite"
Concise: Lists changed files, recommended command, and brief explanation
No false positives: Only suggests benchmarks for performance-critical changes
Actionable: Provides exact commands to copy/paste