Testing
fix-quality - Claude MCP Skill
Run /check-quality, then fix the highest priority quality issue. Creates one fix per invocation. Invoke again for next issue. Use /log-quality-issues to create issues without fixing.
SEO Guide: Enhance your AI agent with the fix-quality tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to run /check-quality, then fix the highest priority quality issue. creates one fix per invocation. inv... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.md# /fix-quality
Fix the highest priority quality infrastructure gap.
## What This Does
1. Invoke `/check-quality` to audit quality gates
2. Identify highest priority gap
3. Fix that one issue
4. Verify the fix
5. Report what was done
**This is a fixer.** It fixes one issue at a time. Run again for next issue. Use `/quality-gates` for full setup.
## Process
### 1. Run Primitive
Invoke `/check-quality` skill to get prioritized findings.
### 2. Fix Priority Order
Fix in this order:
1. **P0**: Missing test runner, missing CI workflow
2. **P1**: Coverage, git hooks, linting, strict TypeScript
3. **P2**: Commitlint, coverage in PRs
4. **P3**: Tool upgrades
### 3. Execute Fix
**No test runner (P0):**
```bash
pnpm add -D vitest @vitest/coverage-v8
```
Create `vitest.config.ts`:
```typescript
import { defineConfig } from 'vitest/config';
export default defineConfig({
test: {
globals: true,
environment: 'node',
coverage: {
provider: 'v8',
reporter: ['text', 'json', 'html'],
},
},
});
```
Add scripts to package.json:
```json
{
"scripts": {
"test": "vitest",
"test:run": "vitest run",
"coverage": "vitest run --coverage"
}
}
```
**No CI workflow (P0):**
Create `.github/workflows/ci.yml`:
```yaml
name: CI
on: [push, pull_request]
jobs:
quality:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: pnpm/action-setup@v4
- uses: actions/setup-node@v4
with:
node-version: 22
cache: 'pnpm'
- run: pnpm install
- run: pnpm typecheck
- run: pnpm lint
- run: pnpm test:run
```
**No git hooks (P1):**
```bash
pnpm add -D lefthook
pnpm lefthook install
```
Create `lefthook.yml`:
```yaml
pre-commit:
parallel: true
commands:
lint:
glob: "*.{ts,tsx}"
run: pnpm eslint {staged_files}
typecheck:
run: pnpm tsc --noEmit
pre-push:
commands:
test:
run: pnpm test:run
```
**TypeScript not strict (P1):**
Update `tsconfig.json`:
```json
{
"compilerOptions": {
"strict": true
}
}
```
### 4. Verify
After fix:
```bash
# Test runner works
pnpm test --run
# Hooks installed
[ -f ".git/hooks/pre-commit" ] && echo "✓ pre-commit hook"
# CI file exists
[ -f ".github/workflows/ci.yml" ] && echo "✓ CI workflow"
```
### 5. Report
```
Fixed: [P0] No test runner configured
Installed:
- vitest
- @vitest/coverage-v8
Created:
- vitest.config.ts
- Added test scripts to package.json
Verified: pnpm test runs successfully
Next highest priority: [P0] No CI workflow
Run /fix-quality again to continue.
```
## Branching
Before making changes:
```bash
git checkout -b infra/quality-$(date +%Y%m%d)
```
## Single-Issue Focus
This skill fixes **one issue at a time**. Benefits:
- Small, reviewable changes
- Easy to verify each fix
- Clear commit history
Run `/fix-quality` repeatedly to work through the backlog.
## Related
- `/check-quality` - The primitive (audit only)
- `/log-quality-issues` - Create issues without fixing
- `/quality-gates` - Full quality setup workflowSignals
Information
- Repository
- phrazzld/claude-config
- Author
- phrazzld
- Last Sync
- 3/2/2026
- Repo Updated
- 3/1/2026
- Created
- 1/25/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
firecrawl-build-onboarding
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
firecrawl-build-scrape
Integrate Firecrawl `/scrape` into product code for single-page extraction. Use when an app already has a URL and needs markdown, HTML, links, screenshots, metadata, or structured page output. Prefer this skill over broader crawl patterns when the feature is page-level.
firecrawl-build-search
Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.
firecrawl-build
Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app — web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.
Related Guides
Mastering Python and TypeScript Development with the Claude Skill Guide
Learn how to use the python typescript guide Claude skill. Complete guide with installation instructions and examples.
Mastering VSCode Extension Development with Claude: A Complete Guide to the TypeScript Extension Dev Skill
Learn how to use the vscode extension dev typescript Claude skill. Complete guide with installation instructions and examples.
Next.js SEO Dev: The Essential Claude Skill for Documented React Development
Learn how to use the nextjs seo dev Claude skill. Complete guide with installation instructions and examples.