本文へ移動
cccskills
無料GitHub で公開

but-performance-tests

Use when creating, changing, running, or debugging shell-based `but` CLI performance scenarios under `crates/but/tests/performance`, including Hyperfine runs, fixture setup, setup-to-test state, and output inspection.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

but CLI performance tests

Read performance framework documentation completely before answering questions or changing performance scenarios. Inspect nearby scenarios and current shared helpers as applicable; README is canonical source for framework behavior, commands, helper APIs, and debugging options.

Workflow for changes

  1. Confirm requested operation and timing boundary.
  2. Inspect closest existing scenarios plus lib.sh and run.sh.
  3. Add or update only scenario's setup.sh and test.sh unless shared behavior is genuinely required.
  4. Prefer real, representative GitButler repository state over toy data.
  5. Keep setup, validation, and ID discovery outside timed operation.
  6. Reuse documented helpers instead of creating parallel fixture, state, output, or timing mechanisms.
  7. List every scenario in top-level performance README's included-scenario list, and update its entry when materially changing scenario.
  8. Run README's shell validation and short single-scenario benchmark.

For usage or debugging questions, answer from current README and scripts. Do not edit files unless user asks for changes.

Guardrails

  • Keep changes inside crates/but/tests/performance/ unless task specifically requests related documentation or skill updates.
  • Preserve two-file scenario contract.
  • Do not add custom timing/statistics code; Hyperfine owns measurement.
  • Do not include fixture setup or compilation in measured command.
  • Do not run all scenarios when user requests or changes only one.
  • Report fixture/setup limitations and unavailable validation explicitly.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

but

無料

Commit, push, branch, and manage version control with GitButler. Use for commits, selective dirty-file or hunk commits, branches, diffs, PRs, history edits, squashes, amends, undo, merge, apply, and unapply. For selected dirty files or hunks, inspect with `but diff`; use compact `but status` for commit order, branch/stack placement, or conflict overview; use `but status -fv` when file/hunk IDs or per-commit file details matter. Replaces git write commands.

日本語の概要は準備中です。原文の説明を表示しています。

gitbutlerapp/gitbutler2.2万2026年10月11日 更新

Use for prompts like "get context for branch", "catch up on this branch", "recover branch context", or "what prior agent work happened here". Skim prior agent work from `but agentlog` captures for a GitButler branch, review / pull request / merge request, or change. Prefer this over generic git branch/diff inspection when the user asks for context, history, prior work, or branch catch-up.

日本語の概要は準備中です。原文の説明を表示しています。

gitbutlerapp/gitbutler2.2万2026年10月11日 更新

Use when adding or modifying CLI command (`but` commands) under `crates/but/src`.

日本語の概要は準備中です。原文の説明を表示しています。

gitbutlerapp/gitbutler2.2万2026年10月11日 更新

Use when changing what users see in an app built on `@gitbutler/ui-react` — Lite, the but.dev web app — adding or restyling a component, modal, form, list, empty state or toast, or writing the words on screen. Not for logic, data or backend work, even inside a UI file.

日本語の概要は準備中です。原文の説明を表示しています。

gitbutlerapp/gitbutler2.2万2026年10月11日 更新

Use when working on React code in `apps/lite` that derives values during render, adds or consumes a context, subscribes to the redux store or a query, or renders lists of row components — and whenever the lite UI is reported slow, laggy, or re-rendering too much. React Compiler does not prevent these regressions; load this skill BEFORE writing such code, not only when debugging it.

日本語の概要は準備中です。原文の説明を表示しています。

gitbutlerapp/gitbutler2.2万2026年10月11日 更新

Use when asked to add before/after screenshots of a Lite UI change to a pull request, when a PR touching apps/lite/ui needs its visual change shown, or when extending the screenshot catalogue in apps/lite/e2e/tests/screenshots.spec.ts. Captures both sides locally against seeded fixtures, publishes the surfaces that changed, and posts them to the PR.

日本語の概要は準備中です。原文の説明を表示しています。

gitbutlerapp/gitbutler2.2万2026年10月11日 更新

gitbutlerapp のスキルをすべて見る

このスキルの問題を報告する