Skills issue-review

📦

issue-review

Name: issue-review
Author: DennisLiuCk

Content revision r1 Safe ⚙️ External commands

Analyze Software Issues with Root Cause Review

Software issue reports often lack enough evidence for a clear fix. This skill guides Claude, Codex, or Claude Code through staged root cause analysis.

Supports: Claude Codex Code(CC)

🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "issue-review" from https://skillstore.io/skills/dennisliuck-issue-review.md and its manifest at https://skillstore.io/api/skills/dennisliuck-issue-review/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/dennisliuck-issue-review.md Signed manifest GET /api/skills/dennisliuck-issue-review/manifest Signed lockfile GET /api/skills/dennisliuck-issue-review/lockfile

Test it

Using "issue-review". A PM reports that users cannot complete checkout in production.

Expected outcome:

A triage summary names the symptom, missing data, likely causes, severity, and whether Git or log analysis should run.

Using "issue-review". A deploy caused checkout failures after a payment dependency update.

Expected outcome:

Likely root cause candidates ranked by evidence.
Relevant files, suspect changes, and affected flow areas.
Recommended fix direction and validation checks.

Using "issue-review". Server logs show repeated timeout errors for one API endpoint.

Expected outcome:

A structured incident report links log signals to likely code paths and lists the next verification steps.

Security Audit

Safe

v8 • 7/6/2026 Open versioned report

The external command findings are false positives caused by Markdown fences and inline code formatting in SKILL.md. The high entropy finding is also a false positive because the file is readable YAML and Markdown with multilingual text and diagrams, not encoded content. No semantic malicious intent or prompt injection attempt was found.

Files scanned

356

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/dennisliuck-issue-review/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/dennisliuck-issue-review/security.svg)](https://skillstore.io/skills/dennisliuck-issue-review?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/dennisliuck-issue-review?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dennisliuck-issue-review/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/dennisliuck-issue-review.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

DennisLiuCk. (2026). issue-review security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dennisliuck-issue-review/audits/8

BibTeX citation

@techreport{dennisliuck-dennisliuck-issue-review-2026,
  author = {DennisLiuCk},
  title = {issue-review security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/dennisliuck-issue-review/audits/8},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "issue-review security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
  - name: "DennisLiuCk"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/dennisliuck-issue-review/audits/8"
identifiers:
  - type: other
    value: "skillstore:dennisliuck-issue-review:audit:8"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Triage Customer Bugs

Turn a customer or PM report into missing questions, severity, and likely technical causes.

Debug Recent Regressions

Compare symptoms with recent code changes and rank suspicious commits or modules.

Investigate Production Alerts

Connect logs, stack traces, and code paths into a root cause report with validation steps.

Try These Prompts

Review a Bug Report

Use issue-review to analyze this bug report: [paste report]. Identify missing information, issue type, severity, and likely causes.

Analyze a Recent Regression

Use issue-review for a recent regression. The issue began after [release or change]. Review likely code areas and recent changes.

Investigate Logs and Stack Traces

Use issue-review with these logs and symptoms: [paste logs]. Connect error patterns to code paths and root cause hypotheses.

Run a Full Root Cause Review

Run a full issue-review workflow for this incident: [context]. Include problem analysis, code investigation, optional Git or log review, root cause, fix guidance, and validation steps.

Best Practices

Provide symptoms, environment, timestamps, expected behavior, and actual behavior.
Include relevant logs, stack traces, and recent release or change context.
Ask for evidence, confidence, and validation steps before implementing a fix.

Avoid

Do not ask for root cause analysis with only a vague phrase like it is broken.
Do not paste secrets, tokens, or customer personal data in logs.
Do not treat hypotheses as confirmed before code and evidence review.

Frequently Asked Questions

Does this skill fix bugs automatically?

No. It produces analysis, likely causes, fix guidance, and validation steps. A developer still applies and tests the fix.

What input works best?

Detailed symptoms, reproduction steps, environment data, timestamps, logs, stack traces, and recent change context work best.

When should Git history analysis run?

Use it when the issue started recently, appeared after a release, or may be linked to a dependency or configuration change.

Can it analyze production incidents?

Yes. It can structure an incident review when you provide symptoms, logs, affected services, and available code context.

Does it require logs?

No. Logs improve confidence, but the workflow can still analyze symptoms, reproduction steps, and code paths.

Is it only for Claude?

No. The listing supports Claude, Codex, and Claude Code, but named agent behavior depends on the active environment.

Developer Details

Author

DennisLiuCk

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/DennisLiuCk/claude-plugin-marketplace/tree/main/plugins/issue-review/skills/issue-review

Ref

72d5025b022c77f7a51bdf5c1637c689c80e89d1

Maintenance freshness

7/18/2026

Usage

8 downloads · 242 views

File structure

📄 SKILL.md

issue-review

Install with my Agent

Agent-readable resources

Test it

Security Audit

Risk Factors

Copy report link

Markdown badge

HTML badge

Embed card

APA citation

BibTeX citation

CITATION.cff

Skillstore Score

What You Can Build

Triage Customer Bugs

Debug Recent Regressions

Investigate Production Alerts

Try These Prompts

Best Practices

Avoid

Frequently Asked Questions

Developer Details