Skip to content
Skills Library
Programming · Review & audit

quality-stack

/quality-stack

Scan a project to detect configured quality and testing tools across JVM (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python ecosystems. Cross-reference against research-backed recommendations and assist with setup. Auto-detects project type(s) including monorepos with mixed ecosystems. Use when user asks to "audit tooling", "recommend tools", "quality stack", "what tools am I missing", "setup eslint", "setup detekt", "add coverage", "add ruff", "configure CI quality pipeline", "scan project tools", "tooling audit", "android tooling", "android quality", "compose testing",

Licence
MIT
Last repository change
14.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
12
Scripts
8
HTML comments
0
URLs in SKILL.md
7
Deprecation

No signals detected. Repository changed on 14.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 8 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/scan_android.py, scripts/scan_cross_cutting.py, scripts/scan_jvm.py, scripts/scan_node.py, scripts/scan_project.py, scripts/scan_python.py, scripts/scan_tooling.py, scripts/shared.py

What it does and when to use it

Scan a project to detect configured quality and testing tools across JVM (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python ecosystems. Cross-reference against research-backed recommendations and assist with setup. Auto-detects project type(s) including monorepos with mixed ecosystems. Use when user asks to "audit tooling", "recommend tools", "quality stack", "what tools am I missing", "setup eslint", "setup detekt", "add coverage", "add ruff", "configure CI quality pipeline", "scan project tools", "tooling audit", "android tooling", "android quality", "compose testing",

Triggers from the description

audit toolingrecommend toolsquality stackwhat tools am I missingsetup eslintsetup detektadd coverageadd ruff
Original author description

Scan a project to detect configured quality and testing tools across JVM (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python ecosystems. Cross-reference against research-backed recommendations and assist with setup. Auto-detects project type(s) including monorepos with mixed ecosystems. Use when user asks to "audit tooling", "recommend tools", "quality stack", "what tools am I missing", "setup eslint", "setup detekt", "add coverage", "add ruff", "configure CI quality pipeline", "scan project tools", "tooling audit", "android tooling", "android quality", "compose testing",

How it works

  1. Pre-flight
  2. Two-Phase Workflow
  3. Priority Classification
  4. Research Documents
  5. Scanner Architecture
  6. References
Original SKILL.md headings · 153 lines, 785 words
SKILL.md preview
---
name: quality-stack
description: >
  Scan a project to detect configured quality and testing tools across JVM
  (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python
  ecosystems. Cross-reference against research-backed recommendations and assist
  with setup. Auto-detects project type(s) including monorepos with mixed
  ecosystems. Use when user asks to "audit tooling", "recommend tools", "quality
  stack", "what tools am I missing", "setup eslint", "setup detekt", "add
  coverage", "add ruff", "configure CI quality pipeline", "scan project tools",
  "tooling audit", "android tooling", "android quality", "compose testing",
  "kmp testing", or "screenshot testing".
disable-model-invocation: true
---

# Quality Stack

Scan a project's build configuration across JVM, Android, Node.js, and Python ecosystems, cross-reference against curated research documents, and assist with tool setup.

## Pre-flight

1. **Run the orchestrator** — it auto-detects ecosystems:
   ```bash
   python3 <skill-path>/scripts/scan_project.py <project-root>
   ```
2. If `"error": "no_ecosystem_detected"`, check `nearby_project_files` for subproject paths.
3. **Monorepo?** — use `--recursive` or `--ecosystem` to force a specific scanner:
   ```bash
   python3 <skill-path>/scripts/scan_project.py --recursive <project-root>
   python3 <skill-path>/scripts/scan_project.py --ecosystem node <project-root>
   ```
4. **Legacy (JVM only)** — `scan_tooling.py` still works as a backwards-compatible wrapper.

## Two-Phase Workflow

### Phase 1: Recommend

1. **Run the scanner** on the project root (see Pre-flight above).

2. **Fetch research documents** via WebFetch — only for detected ecosystems:

   **Android** (when `ecosystems` contains `"android"`):
   ```
   https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/android-ecosystem-tooling.md
   https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/android-testing-ecosystem.md
   ```

   **JVM** (when `ecosystems` contains `"jvm"`):
   ```
   https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/jvm-quality-tools-evaluation.md
   https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/kotlin-spring-boot-testing-ecosystem.md
   ```

   **Node.js** (when `ecosystems` contains `"node"`):
   ```
   https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/node-quality-tools-evaluation.md
   ```

   **Python** (when `ecosystems` contains `"python"`):
   ```
   https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/python-quality-tools-evaluation.md
   ```

   **Cross-cutting** (always):
   ```
   https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/research/cross-cutting-devtools-evaluation.md
   ```

   If WebFetch fails, warn the user and proceed using scanner results + LLM knowledge only.

3. **Cross-reference** scanner output against research recommendations per ecosystem:
   - Identify tools recommended but missing from the project
   - Check `status` field: `disabled` or `config-only` tools need attention
   - Flag outdated or superseded tools
   - Apply ecosystem-specific SKIP rules (see [WORKFLOW.md](WORKFLOW.md))
   - Review `tool_config` for threshold values and settings

4. **Generate the recommendation report** using the format in [WORKFLOW.md](WORKFLOW.md).

### Phase 2: Setup

After presenting the report, present tools for selection using the multi-round
protocol in [WORKFLOW.md](WORKFLOW.md). Group by ecosystem and priority tier.
Include effort estimates. After user completes selection across all rounds:

1. Read the relevant research doc section for setup instructions
2. Apply [Setup Guards](WORKFLOW.md) — resolve versions, check compatibility
3. For each selected tool, apply changes per ecosystem:
   - **JVM**: Add Gradle/Maven plugin, test deps, config files
   - **Node.js**: `pnpm add -D`, tsconfig edits, config file creation
   - **Python**: `uv add --dev`, pyproject.toml edits, config file creation
   - **Cross-cutting**: CI/CD workflow steps, Lefthook config, EditorConfig
4. **Verify each tool** after configuration — run the tool's check command,
   verify filter patterns against actual codebase paths, and check for config
   inheritance conflicts. See [WORKFLOW.md](WORKFLOW.md) Post-Setup Verification.
5. Re-run the scanner to confirm all tools detected

## Priority Classification

| Priority | Criteria |
|----------|----------|
| **NOW** | Essential missing tools, zero-dependency additions |
| **SOON** | High-value additions requiring minor setup |
| **LATER** | Nice-to-have with prerequisites |
| **SKIP** | Not applicable (wrong ecosystem, incompatible version, deprecated) |

**Ecosystem-aware rules** — see [WORKFLOW.md](WORKFLOW.md) for full classification tables per ecosystem.

**Key rules:**
- Android Compose project: NOW Compose UI testing, SOON Roborazzi; SKIP Espresso
- Android KMP project: NOW commonTest setup, NOW Turbine; SOON Ktor MockEngine
- Android no lint config: NOW Android Lint baseline; SOON custom lint rules
- Android Kotlin 2.4+: NOW remove `StrongSkipping`/`IntrinsicRemember` flags (compiler errors)
- Android KMP module on `com.android.library`: NOW migrate to `com.android.kotlin.multiplatform.library`
- Android Compose-only app on Navigation 2.x: SOON Navigation 3 (`androidx.navigation3`)
- Superseded coordinates (flag, don't just bump): `android-junit5` → `de.mannodermaus.android-junit`;
  `mockwebserver` → `mockwebserver3`; Detekt 2.x → `dev.detekt`; Room 3 → `androidx.room3`
- JVM Pure Kotlin: SKIP Error Prone, SpotBugs; JVM Pure Java: SKIP Detekt, ktlint, MockK
- JVM Kotlin/KMP coverage: prefer Kover over JaCoCo; JaCoCo for mixed Java/Kotlin or Maven
- JVM Kotlin mutation testing: `pitest-kotlin` is archived — maintained filter is paid (Arcmutate)
- JVM Spring Boot 4+: SKIP REST Assured, NOW MockMvcTester
- Node.js no linter: NOW ESLint; no formatter + no Biome: NOW Prettier
- Node.js TypeScript not strict: NOW enable strict
- Python no linter: NOW Ruff; no type checker + has type annotations: NOW mypy

### Cross-Cutting Tools

| Tool | When to Recommend | Priority |
|------|------------------|----------|
| Lefthook | No git hook manager + has linters | SOON |
| commitlint | No commit conventions + has team | LATER |
| EditorConfig | Missing `.editorconfig` | NOW |
| Renovate/Dependabot | No dependency automation | SOON |
| Trivy/gitleaks | No security scanning | SOON |

## Research Documents

Fetch via WebFetch at runtime — only for detected ecosystems:

- **Android Ecosystem Tooling**: `android-ecosystem-tooling.md`
- **Android Testing Ecosystem**: `android-testing-ecosystem.md`
- **JVM Quality Tools**: `jvm-quality-tools-evaluation.md`
- **JVM Testing Ecosystem**: `kotlin-spring-boot-testing-ecosystem.md`
- **Node.js Quality Tools**: `node-quality-tools-evaluation.md`
- **Python Quality Tools**: `python-quality-tools-evaluation.md`
- **Cross-Cutting Tools**: `cross-cutting-devtools-evaluation.md`

## Scanner Architecture

```
scripts/
  scan_project.py          # Orchestrator — auto-detects + merges
  scan_jvm.py              # JVM scanner (Gradle/Maven)
  scan_android.py          # Android scanner (AGP/Compose/KMP)
  scan_node.py             # Node.js/TypeScript scanner
  scan_python.py           # Python scanner
  scan_cross_cutting.py    # Cross-cutting tools (CI, hooks, security)
  shared.py                # Shared utilities
  scan_tooling.py          # Legacy wrapper → scan_jvm.py
```

## References

- **Workflow**: See [WORKFLOW.md](WORKFLOW.md) for classification rules and report format
- **Examples**: See [EXAMPLES.md](EXAMPLES.md) for realistic audit scenarios
- **Troubleshooting**: See [TROUBLESHOOTING.md](TROUBLESHOOTING.md) for scanner issues
Files in this package (12)
  • EXAMPLES.md 28 KB
  • SKILL.md 8 KB
  • TROUBLESHOOTING.md 15 KB
  • WORKFLOW.md 38 KB
  • scripts/scan_android.py 30 KB
  • scripts/scan_cross_cutting.py 18 KB
  • scripts/scan_jvm.py 28 KB
  • scripts/scan_node.py 19 KB
  • scripts/scan_project.py 13 KB
  • scripts/scan_python.py 24 KB
  • scripts/scan_tooling.py 1 KB
  • scripts/shared.py 2 KB

Versions

The database has no other skills named quality-stack.

Database snapshot: 13.11.2026 · package version 00d38349c6bd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100build-and-test
    Mapping a multi-module Gradle project before guessing a task name, building a variant, running JVM vs on-device tests, and turning a JaCoCo coverage report into the specific lines that need a test. Use when building, testing, or checking coverage for an Android/Gradle project.
  • 100agp-9-upgrade
    Upgrades, or migrates, an Android project to use Android Gradle Plugin (AGP) version 9. Do not use this skill for migrating Kotlin Multiplatform (KMP) projects.
  • 90Android Project
    Create or repair an Android Gradle project on this phone: modules, AGP/Gradle versions, manifest, package name, and a first build. Use when starting a new app or when the project structure is broken.
  • 100android-agp-upgrade
    Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
  • 100kotlin-tooling-agp9-migration
    Migrates Kotlin Multiplatform (KMP) projects to Android Gradle Plugin 9.0+. Handles plugin replacement (com.android.kotlin.multiplatform.library), module splitting, DSL migration, and the new default project structure. Use when upgrading AGP, when build fails due to KMP+AGP…
  • 100project-check
    Existing project health scan — audits Infrastructure, Security, Quality, and Harness setup. Read-only. Use when: '/project-check', 'project health check', 'project audit', 'what\\'s missing', 'analyze my project', 'check setup'. Ends with /project-init and /setup…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.