dev-quality-report

Dev Quality Report

This skill generates persistent code quality reports.

When to Use

• During /quality-check command
• When quality check is requested during /end
• When analyzing code quality for specific paths
• Independent of any active session

Input

• paths: List of paths to analyze (default: repo root)
• options:
  • include: Glob patterns to include
  • exclude: Glob patterns to exclude
  • defaultExcludes: boolean (default: true) - Apply default ignore rules

Responsibilities

• Ask user which paths to analyze (if not provided)
• Apply default ignore rules (unless disabled)
• Generate unique reportId (8-char hex)
• Generate report path: .claude/dev-sessions/quality-reports/YYYYMMDD-HHmm-qa-{reportId}.md
• Write initial report with Status: PENDING
• Call code-quality-analyzer agent in read-only mode
• Rewrite report with full analysis and Status: DONE or ABORTED
• Return report path and summary

Default Ignore Rules

Always ignored unless defaultExcludes: false:

• **/node_modules/**
• **/.git/**
• **/dist/**, **/build/**, **/.next/**, **/.vite/**
• **/coverage/**, **/.turbo/**, **/.cache/**
• **/tmp/**, **/.tmp/**
• **/package-lock.json, **/pnpm-lock.yaml, **/yarn.lock
• **/*.min.*

MUST

• Use artifact-fs-manager for all file operations
• Never modify repository source files
• Never change any session Status
• Always set report Status to PENDING before analysis
• Always set report Status to DONE or ABORTED after

MUST NOT

• Modify any source code files
• Install or change dependencies
• Change session status
• Run commands that modify the codebase

Process

Step 1: Determine Paths

If paths not provided:

1. Ask user: "Which paths should I analyze? (default: repo root)"
2. Accept user input or use default

Step 2: Apply Ignore Rules

1. Start with default ignore patterns (if defaultExcludes: true)
2. Add any additional exclude patterns
3. Apply include patterns to narrow scope