How do I install the Log Product Standards Issues skill?

Run npx skillmds add majiayu000/log-product-standards-issues in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Log Product Standards Issues safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Log Product Standards Issues?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Log Product Standards Issues free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Log Product Standards Issues?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Log Product Standards Issues by majiayu000

Name: Log Product Standards Issues
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

/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:

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

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

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

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:hello@mistystep.io">Contact</a>

Missing Releases Page

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

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

---name: log-product-standards-issuesdescription: Run /check-product-standards, then create GitHub issues for all findings. Invoked by /groom as P1 fundamental check.--- # /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:hello@mistystep.io">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

Frequently asked questions