configure

Configure

Configure Rust development tools. Scaffold configuration files with sensible defaults or edit existing ones.

Procedure

1. Parse the tool argument. If no argument, detect existing configs and present a menu.

2. Detection phase — check for existing config files:

   • clippy.toml or [lints.clippy] in Cargo.toml
   • rustfmt.toml
   • .rust-analyzer.json
   • rust-toolchain.toml Report what's found and what's missing.

3. If no argument: Present the detection results and ask which tool to configure. Offer "all" to scaffold everything.

configure clippy

4. Create clippy.toml with sensible defaults:

   # Lint configuration for clippy
   cognitive-complexity-threshold = 25
   too-many-arguments-threshold = 7
   

5. If Cargo.toml exists, suggest adding lint configuration:

   [lints.clippy]
   all = "warn"
   pedantic = "allow"
   nursery = "allow"
   

6. If config already exists, show current settings and ask before overwriting.

configure rustfmt

4. Create rustfmt.toml with sensible defaults:

   edition = "2024"
   max_width = 100
   use_field_init_shorthand = true
   

5. If config already exists, show current settings and ask before overwriting.

configure rust-analyzer

4. Create .rust-analyzer.json with sensible defaults:

   {
       "check": {
           "command": "clippy"
       },
       "cargo": {
           "features": "all"
       }
   }
   

5. If config already exists, show current settings and ask before overwriting.

configure all

4. Run all three configurations in sequence (clippy → rustfmt → rust-analyzer), respecting existing configs.
5. Summarize what was created/modified.

Composition

This skill is forward-looking: the canonical triage procedure lives in skills/diagnostic-review/SKILL.md and is invoked via Skill(skill: "rust-toolkit:diagnostic-review") with pass: configure. Per-pass invocation wiring lands in a later chore (per the Path B cut-scope decision); for now the skill body above inlines the procedure that matches the legacy /configure command behavior.