home / skills / phrazzld / claude-config / log-quality-issues

log-quality-issues skill

safe

/skills/log-quality-issues

This skill audits quality findings via /check-quality, avoids duplicates, and creates prioritized GitHub issues for each finding.

npx playbooks add skill phrazzld/claude-config --skill log-quality-issues

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

Files (1)

SKILL.md

2.5 KB

---
name: log-quality-issues
description: |
  Run /check-quality, then create GitHub issues for all findings.
  Issues are created with priority labels and structured format.
  Use /fix-quality instead if you want to fix issues immediately.
effort: medium
---

# /log-quality-issues

Run quality gates audit and create GitHub issues for all findings.

## What This Does

1. Invoke `/check-quality` to audit quality infrastructure
2. Parse findings by priority (P0-P3)
3. Check existing issues to avoid duplicates
4. Create GitHub issues for each finding

**This is an issue-creator.** It creates work items, not fixes. Use `/fix-quality` to fix issues.

## Process

### 1. Run Primitive

Invoke `/check-quality` skill to get structured findings.

### 2. Check Existing Issues

```bash
gh issue list --state open --label "domain/quality" --limit 50
```

### 3. Create Issues

For each finding:

```bash
gh issue create \
  --title "[P0] No test runner configured" \
  --body "$(cat <<'EOF'
## Problem
No testing framework (Vitest/Jest) is configured. Code changes cannot be validated.

## Impact
- Regressions go undetected
- Refactoring is dangerous
- CI cannot verify changes
- No confidence in deployments

## Suggested Fix
Run `/fix-quality` or manually:
```bash
pnpm add -D vitest @vitest/coverage-v8
```

Then create `vitest.config.ts` with coverage enabled.

---
Created by `/log-quality-issues`
EOF
)" \
  --label "priority/p0,domain/quality,type/chore"
```

### 4. Issue Format

**Title:** `[P{0-3}] Quality gap description`

**Labels:**
- `priority/p0` | `priority/p1` | `priority/p2` | `priority/p3`
- `domain/quality`
- `type/chore`

**Body:**
```markdown
## Problem
What quality infrastructure is missing

## Impact
Risk and consequences of the gap

## Suggested Fix
Commands or skill to run

---
Created by `/log-quality-issues`
```

## Priority Mapping

| Gap | Priority |
|-----|----------|
| No test runner | P0 |
| No CI workflow | P0 |
| No coverage configured | P1 |
| No git hooks | P1 |
| No linting | P1 |
| TypeScript not strict | P1 |
| No commitlint | P2 |
| No coverage in PRs | P2 |
| Tool upgrade opportunities | P3 |

## Output

After running:
```
Quality Issues Created:
- P0: 2 (no tests, no CI)
- P1: 3 (coverage, hooks, linting)
- P2: 2 (commitlint, PR coverage)
- P3: 1 (tool upgrades)

Total: 8 issues created
View: gh issue list --label domain/quality
```

## Related

- `/check-quality` - The primitive (audit only)
- `/fix-quality` - Fix quality infrastructure
- `/quality-gates` - Full quality setup workflow
- `/groom` - Full backlog grooming

Overview

This skill runs a quality gates audit and automatically creates GitHub issues for each finding, organized by priority. It reports gaps in testing, CI, coverage, linting, and related quality infrastructure so teams can triage and track remediation work.

How this skill works

The skill invokes the /check-quality primitive to collect structured findings, groups them by priority (P0–P3), checks existing open issues to avoid duplicates, and creates new GitHub issues for any uncovered gaps. Each created issue uses a consistent title, labels (priority/domain/type), and a structured body describing Problem, Impact, and a Suggested Fix.

When to use it

After running static or automated audits and you need tracked action items for each gap
When onboarding a repository to capture missing quality infrastructure as issues
Before a release to ensure quality gaps are visible and assigned
When you prefer creating work items rather than applying automatic fixes
As part of a periodic quality review or sprint planning session

Best practices

Run /check-quality first to get structured findings; use /fix-quality only when you want automated changes
Review existing open issues with label domain/quality to prevent duplicates
Prioritize triage by the P0–P3 mapping so critical gaps are addressed first
Include maintainers or a team in issue assignees or project boards after creation
Keep Suggested Fix steps actionable and reference the /fix-quality skill for automated remediation

Example use cases

Audit a new repo and create issues for missing test runner, CI workflow, and coverage
Generate a backlog of quality chores before a major refactor or release
Surface low-effort upgrade opportunities as P3 issues for later grooming
Ensure missing pre-commit hooks or commitlint are tracked as P1/P2 work items
Create issues for coverage gaps so PRs enforce coverage thresholds

FAQ

Will this skill modify code or configuration?

No. This skill only creates GitHub issues describing problems and suggested fixes. Use /fix-quality to apply automated changes.

How does it avoid duplicate issues?

It lists open issues labeled domain/quality and compares findings before creating new issues to reduce duplicates.