nw-rigor

Persist nWave quality-vs-token profiles to global or project JSON config.

Updated Mar 18, 2024
One-click install
npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-rigor-v1bh0r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-rigor
Source: https://github.com/v1bh0r/precise-ledger-pro/tree/main/nWave/skills/nw-rigor
Command: npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-rigor-v1bh0r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Selects and persists a quality-vs-token-consumption profile for nWave at either global or per-project scope to tune agent behavior and validation rigor.

Core Features & Use Cases

  • Supports the preset profiles lean, standard, thorough, exhaustive, custom, and inherit.
  • Persists configuration globally at ~/.nwave/global-config.json or per-project at .nwave/des-config.json.
  • Influences agent_model, reviewer_model, review_enabled, tdd_phases, mutation_enabled, and refactor_pass for all wave commands.
  • Use case: align rigor to project needs, optimize token cost, and control mutation testing and code review depth.

Quick Start

Run /nw-rigor to start the interactive profile chooser, or supply a profile name (lean, standard, thorough, exhaustive, custom, inherit) for a quick switch.

Frequently Asked Questions about nw-rigor

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

FAQPage Schema
How do I configure nWave TDD phases and mutation testing rigor?

You configure nWave TDD phases and mutation testing by selecting a quality profile that maps settings for tdd_phases, mutation_enabled, and review policies directly into the target JSON configuration files.

What are the differences between lean, standard, thorough, and exhaustive code review profiles?

Lean, standard, thorough, and exhaustive are preset nWave profiles that scale quality versus token consumption, directly affecting agent models, code review depth, TDD phases, and mutation testing. Custom and inherit profiles offer further flexibility.

Can I set a global nWave configuration or does it need to be per-project?

You can persist nWave configuration globally at ~/.nwave/global-config.json or per-project at .nwave/des-config.json. The skill validates the chosen scope and writes the full profile while preserving all other top-level keys.

How do I optimize token cost for agent models without disabling code review entirely?

To optimize token cost, switch to the lean or standard nWave profile to adjust agent_model and reviewer_model settings. This reduces token consumption while keeping review_enabled active for essential code review policies.

Does switching nWave rigor profiles overwrite existing config JSON settings?

Switching nWave rigor profiles does not overwrite unrelated settings. The process reads existing config, validates scope, maps the new profile settings, and writes the JSON file while preserving all other top-level keys.