home / skills / levnikolaevich / claude-code-skills / ln-740-quality-setup

ln-740-quality-setup skill

/ln-740-quality-setup

This skill coordinates quality tooling setup by detecting tech stacks, checking existing configs, and delegating to specialized workers for rapid integration.

npx playbooks add skill levnikolaevich/claude-code-skills --skill ln-740-quality-setup

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

5.5 KB

---
name: ln-740-quality-setup
description: Coordinates linters, pre-commit hooks, and test infrastructure setup
---

> **Paths:** File paths (`shared/`, `references/`, `../ln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.

# ln-740-quality-setup

**Type:** L2 Domain Coordinator
**Category:** 7XX Project Bootstrap
**Parent:** ln-700-project-bootstrap

Coordinates code quality tooling configuration for the project.

---

## Purpose & Scope

**Does:**
- Detects project technology stack (TypeScript/React, .NET, Python)
- Checks for existing quality configurations
- Delegates to specialized workers for each quality aspect
- Verifies final configuration works correctly

**Does NOT:**
- Generate configuration files directly (workers do this)
- Modify source code
- Run in isolation (requires ln-720 structure first)

---

## When to Use

| Trigger | Action |
|---------|--------|
| After ln-720-structure-migrator completes | Automatic delegation from ln-700 |
| Manual quality setup needed | Invoke directly with project path |
| Existing project needs quality tools | Run with existing config detection |

---

## Workflow Overview

| Phase | Action | Output |
|-------|--------|--------|
| 1 | Stack Detection | Identified technologies |
| 2 | Existing Config Check | Skip/merge/replace decisions |
| 3 | Parallel Delegation | Worker invocations |
| 4 | Verification | Working quality pipeline |

---

## Phase 1: Stack Detection

Detect project technologies to determine which quality tools to configure.

**Detection Rules:**

| File Pattern | Technology | Linter Stack |
|--------------|------------|--------------|
| `package.json` + `tsconfig.json` | TypeScript/React | ESLint + Prettier |
| `*.csproj` or `*.sln` | .NET | editorconfig + Roslyn |
| `pyproject.toml` or `requirements.txt` | Python | Ruff |
| Multiple detected | Mixed | Configure all detected |

**Actions:**
1. Glob for technology indicators
2. Build technology list
3. Log detected stack to user

---

## Phase 2: Existing Configuration Check

Before delegating, check what configurations already exist.

**Config Files to Check:**

| Technology | Config Files |
|------------|--------------|
| TypeScript | `eslint.config.*`, `.prettierrc*`, `tsconfig.json` |
| .NET | `.editorconfig`, `Directory.Build.props` |
| Python | `ruff.toml`, `pyproject.toml [tool.ruff]` |
| Pre-commit | `.husky/`, `.pre-commit-config.yaml` |
| Tests | `vitest.config.*`, `pytest.ini`, `*.Tests.csproj` |

**Decision Matrix:**

| Existing Config | Action | Confirmation |
|-----------------|--------|--------------|
| None found | Create new | No |
| Partial found | Merge (add missing) | Ask user |
| Complete found | Skip | Inform user |
| User requests replace | Backup + replace | Yes |

---

## Phase 3: Parallel Delegation

Invoke workers for each quality aspect. Workers can run in parallel as they configure independent tools.

**Delegation Order:**

```
ln-740 (this)
    |
    +---> ln-741-linter-configurator
    |         - ESLint/Prettier (TypeScript)
    |         - editorconfig/Roslyn (.NET)
    |         - Ruff (Python)
    |
    +---> ln-742-precommit-setup
    |         - Husky + lint-staged (Node.js)
    |         - pre-commit framework (Python)
    |         - commitlint
    |
    +---> ln-743-test-infrastructure
              - Vitest (TypeScript)
              - xUnit (.NET)
              - pytest (Python)
```

Pass detected stack and existing configs to workers via direct Skill tool invocation.

---

## Phase 4: Verification

After all workers complete, verify the quality pipeline works.

**Verification Steps:**

| Check | Command | Expected |
|-------|---------|----------|
| Lint runs | `npm run lint` / `ruff check .` / `dotnet format --verify-no-changes` | No errors |
| Format runs | `npm run format:check` / `ruff format --check` | No changes needed |
| Tests run | `npm test` / `pytest` / `dotnet test` | Sample tests pass |
| Hooks work | Create test commit | Hooks trigger |

**On Failure:**
1. Log specific failure
2. Suggest fix or re-run specific worker
3. Do NOT mark as complete until verification passes

---

## Critical Rules

> **RULE 1:** Never overwrite existing user configurations without explicit confirmation.

> **RULE 2:** Workers run AFTER stack detection - do not invoke workers without knowing the stack.

> **RULE 3:** Verification phase is MANDATORY - quality setup is not complete until tools run successfully.

> **RULE 4:** eslint-config-prettier is REQUIRED when both ESLint and Prettier are configured.

---

## Definition of Done

- [ ] All detected technology stacks have appropriate quality tools
- [ ] Existing configurations preserved or backed up
- [ ] Lint command runs without errors
- [ ] Format command runs without errors
- [ ] Test command runs and sample tests pass
- [ ] Pre-commit hooks trigger on test commit
- [ ] User informed of all installed tools and commands

---

## Reference Files

| File | Purpose |
|------|---------|
| [stack_detection.md](references/stack_detection.md) | Detailed detection rules |
| [verification_checklist.md](references/verification_checklist.md) | Full verification checklist |

---

## Error Handling

| Error | Cause | Resolution |
|-------|-------|------------|
| No stack detected | Empty project | Ask user for intended stack |
| Worker failed | Missing dependencies | Install prerequisites, retry |
| Verification failed | Config error | Check specific tool output, fix |
| Hooks not working | Git not initialized | Run `git init` first |

---

**Version:** 2.0.0
**Last Updated:** 2026-01-10

Overview

This skill coordinates project code quality tooling by detecting the technology stack, checking existing configurations, delegating setup to specialized workers, and verifying the resulting quality pipeline. It orchestrates linters, pre-commit hooks, and test infrastructure without directly modifying source code. The skill enforces safe operations (never overwrite without consent) and requires the project structure baseline to be present.

How this skill works

It globs the repository for indicators (package.json, tsconfig, pyproject.toml, .csproj/.sln, etc.) to build a detected technology list, then inspects for existing config files. Based on detection it invokes dedicated workers in parallel to configure linters, pre-commit hooks, and test frameworks, passing the detected stack and existing-config metadata. Finally it runs verification steps to ensure lint, format, test commands and hooks execute successfully.

When to use it

After initial project structure bootstrap (ln-720) to add quality tooling
When onboarding an existing repository that needs consistent linters and hooks
When you want an automated, non-destructive audit and setup of quality configs
When migrating to or adding new language/tool support (TypeScript, Python, .NET)
Before CI enablement to ensure local quality gates are working

Best practices

Run this skill after the project structure migrator to ensure expected layout
Review detected stack results and confirm merge vs replace when partial configs exist
Always back up or confirm replacement for any existing user configs
Ensure git is initialized before verification so hooks can be tested
Fix worker-reported dependency issues and re-run failing workers instead of skipping verification

Example use cases

Add ESLint, Prettier, Husky/lint-staged, and Vitest to a new TypeScript/React repo
Detect Python code and configure Ruff, pre-commit hooks, and pytest scaffolding
Add .editorconfig and Roslyn rules for a mixed .NET/TypeScript monorepo while preserving existing configs
Run a non-destructive audit that suggests missing quality files and then applies agreed changes
Verify lint, format, test commands and that pre-commit hooks run on a test commit

FAQ

Will this skill overwrite my existing configuration files?

No — it never overwrites user configurations without explicit confirmation; partial merges are suggested and replacements require user approval.

Can it run if the project structure step was not performed?

It expects the structure baseline; if no stack indicators are found it will ask the user for the intended stack instead of proceeding blindly.