🎯

ln-740-quality-setup

🎯Skill

from levnikolaevich/claude-code-skills

VibeIndex|
What it does

Configures code quality tools by detecting project stack, checking existing configurations, and delegating setup to specialized workers.

πŸ“¦

Part of

levnikolaevich/claude-code-skills(85 items)

ln-740-quality-setup

Installation

Claude CodeAdd plugin in Claude Code
/plugin add levnikolaevich/claude-code-skills
git cloneClone repository
git clone https://github.com/levnikolaevich/claude-code-skills.git ~/.claude/skills
πŸ“– Extracted from docs: levnikolaevich/claude-code-skills
11Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

Coordinates linters, pre-commit hooks, and test infrastructure setup

Overview

# 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

More from this repository10

πŸͺ
levnikolaevich-claude-code-skillsπŸͺMarketplace

Official marketplace for Agile Linear Workflow plugin - complete end-to-end automation for software development teams using Linear. Includes 7XX Project Bootstrap series for technology-agnostic project migration.

🎯
ln-140-test-docs-creator🎯Skill

Generates comprehensive test documentation with testing strategy and test organization structure for software projects.

🎯
ln-110-project-docs-coordinator🎯Skill

Coordinates project documentation by gathering context once, detecting project type, and delegating document creation to 5 specialized workers.

🎯
ln-114-frontend-docs-creator🎯Skill

Generates design guidelines documentation for frontend projects with WCAG 2.1 compliance when a frontend framework is detected.

🎯
ln-113-backend-docs-creator🎯Skill

Generates backend documentation files (API spec and database schema) automatically when backend or database technologies are detected in a project.

🎯
ln-610-code-comments-auditor🎯Skill

Audits code comments and docstrings across 6 quality categories, generating a comprehensive compliance score and actionable recommendations for improvement.

🎯
ln-115-devops-docs-creator🎯Skill

Generates a comprehensive runbook.md for DevOps setup, dynamically tailored to project's Docker configuration and deployment specifics.

🎯
ln-772-error-handler-setup🎯Skill

Configures global exception handling middleware for .NET and Python backend applications with standardized error responses.

🎯
ln-120-reference-docs-creator🎯Skill

Generates reference documentation structure and smart documents for project tech stack, creating only justified architectural decision records and guides.

🎯
ln-625-dependencies-auditor🎯Skill

Audits dependencies for outdated packages, unused imports, unnecessary libraries, and custom implementations, providing actionable recommendations.