benchmark

Compare full versus minimal dotforge configurations across detected stacks using benchmark tasks in isolated worktrees.

8|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/luiseiman/dotforge --skill benchmark-luiseiman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: benchmark
Source: https://github.com/luiseiman/dotforge/tree/main/skills/benchmark
Command: npx skills add https://github.com/luiseiman/dotforge --skill benchmark-luiseiman

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This skill helps teams evaluate how full versus minimal dotforge configurations affect task execution, reliability, and maintenance across multiple stacks, enabling informed configuration decisions.

## Core Features & Use Cases

  • Compare the effectiveness of full vs minimal dotforge configurations across project stacks.
  • Automate the creation of two isolated worktrees and execute standardized tasks to surface configuration differences.
  • Generate actionable insights and metrics to guide governance and tooling decisions in multi-repo environments.

### Quick Start Create two git worktrees and run the benchmark task prompts for both configurations as described in the steps.

Frequently Asked Questions about benchmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I benchmark dotforge configuration quality across different project stacks?

To benchmark dotforge configuration quality, this Skill isolates full and minimal configurations in two separate git worktrees, runs standardized tasks, and compares execution results across stacks detected from .claude manifests. It surfaces configuration differences to guide governance decisions.

What do I need to compare full versus minimal dotforge configurations?

Comparing full versus minimal dotforge configurations requires a git repository containing .claude/settings.json, a CLAUDE.md file, and standardized prompts located under tests/benchmark-tasks. The Skill automates worktree creation and task execution once these inputs exist.

How do git worktrees help evaluate configuration differences?

Git worktrees provide isolated environments to simultaneously test full and minimal dotforge configurations. By running identical benchmark tasks in each worktree, the Skill captures execution metrics that reveal how each configuration impacts reliability and maintenance.

Can I use this benchmarking approach for multi-repo environments?

Yes, this benchmarking approach supports multi-repo environments by detecting stacks from .claude manifests and applying standardized tests across repositories. It generates actionable insights to guide tooling decisions in environments with varying configuration depths.

When should I run a dotforge configuration benchmark?

Run a dotforge configuration benchmark when evaluating how full versus minimal configurations affect task execution and reliability. It is designed for teams making informed configuration and governance decisions across multiple stacks in a multi-repo environment.

Why do my dotforge configurations behave differently across project stacks?

Dotforge configurations behave differently due to varying stack requirements detected from .claude manifests. Benchmarking full versus minimal setups in isolated worktrees surfaces these execution differences, helping identify the most reliable configuration for each stack.