home / skills / phrazzld / claude-config / log-product-standards-issues

log-product-standards-issues skill

safe

/skills/log-product-standards-issues

This skill audits product standards and automatically opens GitHub issues for each gap discovered by the /check-product-standards audit.

npx playbooks add skill phrazzld/claude-config --skill log-product-standards-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-product-standards-issues
description: |
  Run /check-product-standards, then create GitHub issues for all findings.
  Invoked by /groom as P1 fundamental check.
effort: medium
---

# /log-product-standards-issues

Audit product standards compliance and create GitHub issues for gaps.

## Process

### Step 1: Run Audit

```
Skill("check-product-standards")
```

### Step 2: Create Issues

For each missing or broken requirement:

```bash
gh issue create \
  --title "[P1] [Title]" \
  --label "priority/p1" \
  --label "domain/product-standards" \
  --label "type/chore" \
  --body "$(cat <<'EOF'
## Problem
[What's missing or broken]

## Requirement
[Link to /check-product-standards requirement]

## Suggested Fix
[Code snippet or next steps]

## Impact
Users cannot [know version / identify maker / get support].
This is a baseline shipping requirement.

---
Created by `/log-product-standards-issues`
EOF
)"
```

## Common Issues

### Missing Version Display

```markdown
Title: [P1] Add version display to footer
Labels: priority/p1, domain/product-standards, type/chore

Problem: No visible version number in the application.

Suggested Fix:
1. Add NEXT_PUBLIC_APP_VERSION to next.config.js
2. Display in footer: `v{process.env.NEXT_PUBLIC_APP_VERSION}`
3. Link to /releases or GitHub releases page
```

### Missing Attribution

```markdown
Title: [P1] Add Misty Step attribution to footer
Labels: priority/p1, domain/product-standards, type/chore

Problem: No "A Misty Step project" attribution visible.

Suggested Fix:
Add to footer:
<a href="https://mistystep.io" target="_blank" rel="noopener noreferrer">
  A Misty Step project
</a>
```

### Missing Contact Link

```markdown
Title: [P1] Add contact/support link
Labels: priority/p1, domain/product-standards, type/chore

Problem: No way for users to contact support or report issues.

Suggested Fix:
Add to footer:
<a href="mailto:[email protected]">Contact</a>
```

### Missing Releases Page

```markdown
Title: [P1] Create releases page or link to GitHub releases
Labels: priority/p1, domain/product-standards, type/chore

Problem: Version number doesn't link to changelog/releases.

Suggested Fix:
Either:
1. Create /releases page with changelog
2. Link version to GitHub releases: https://github.com/MistyStep/[repo]/releases
```

## Output

Issues created in GitHub with:
- Priority: P1 (fundamentals)
- Domain: product-standards
- Type: chore

## Related

- `/check-product-standards` — The audit skill
- `/groom` — Orchestrates all issue creators

Overview

This skill audits product-standards compliance and opens GitHub issues for each missing or broken requirement. It is invoked as a fundamental P1 check and ensures baseline shipping requirements (version, attribution, contact, releases) are tracked as actionable work. Issues are created with consistent titles, labels, and a structured body describing problem, requirement, suggested fix, and impact.

How this skill works

First the skill runs the product-standards audit (/check-product-standards) to collect findings. For each failing requirement it creates a GitHub issue using a standard template, applying priority/p1, domain/product-standards, and type/chore labels. Each issue includes a clear problem statement, a link to the audited requirement, suggested fixes or code snippets, and the user-impact explanation.

When to use it

As part of /groom to enforce baseline shipping standards
Before a release to ensure visible versioning and support links
When onboarding a repository to ensure product attribution and support flow
During QA audits to convert gaps into tracked work
If a security or compliance checklist references product-standards

Best practices

Run /check-product-standards regularly and review findings before mass-creating issues
Provide concrete suggested fixes or code snippets in the issue body to reduce triage time
Include repository-specific links (releases page or contact address) when suggesting fixes
Prioritize addressing P1 product-standards issues before public releases
Use consistent labeling and title format to make automation and filtering easier

Example use cases

Add visible app version to the footer and link it to releases
Insert required project attribution into site footer
Add a contact/support mailto link or support page link in the UI
Create a /releases changelog page or add a link to the GitHub releases page
Convert audit findings into prioritized chores for the product team

FAQ

Will the skill create duplicate issues?

The skill creates one issue per finding from the audit. Deduplicate by reviewing existing open issues or adjust the audit to skip already-tracked items.

Can I customize labels or issue text?

Yes. Update the issue creation template to change titles, labels, or body content to match your repo conventions.