issue-verify

Name: issue-verify
Availability: InStock
Author: cc-claws

Update issue status records and verification history in structured markdown files.

2|Updated Jun 25, 2026

Search Tags:#markdown #regression #issue-tracking #reopen #bug-verification #status-management

Ready to run

npx skills add https://github.com/cc-claws/cc-code --skill issue-verify-cc-claws

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-verify
Source: https://github.com/cc-claws/cc-code/tree/main/.claude/skills/issue-verify
Command: npx skills add https://github.com/cc-claws/cc-code --skill issue-verify-cc-claws

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps track and record issue status changes when someone asks to verify a fix, reopen a bug, mark partial progress, or close an issue, while preserving the original user intent and the full resolution history.

Core Features & Use Cases

State-aware updates: Handles Open, Pending, Partial, Reopen, Fixed, Verified, and Closed transitions with the right validation flow.
Verification capture: Records whether a fix actually worked, what still fails, and any regressions or partial outcomes.
History preservation: Appends transition notes and repair context instead of overwriting prior records, which is useful for bug triage and retrospective review.

Quick Start

Tell the assistant which issue to update and what outcome you want, then share any verification details, symptoms, or status change you want recorded.

Frequently Asked Questions about issue-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I record regression checks and reopen a bug in markdown issue files?▼

Yes, you can track partial fixes by applying state-aware updates that transition the issue to a Partial status. The verification capture records what still fails and any partial outcomes, appending transition notes to the structured markdown issue files rather than overwriting prior context.

How does issue status management handle state transitions for verified bugs?▼

Yes, issue closure decisions are supported by validating the transition to a Closed state. The Skill captures the final verification details, symptoms, and status changes, appending them as transition notes to ensure the full resolution history is preserved for retrospective review.

What is the best way to preserve issue resolution history when updating bug verification status?▼

The best way to preserve issue resolution history is by appending state transition notes and repair context instead of overwriting prior records. This ensures structured markdown issue files maintain complete verification details and original user intent for accurate bug triage and retrospective review.

Can I use structured markdown to track issue feedback and closure decisions?▼

Yes, you can use structured markdown to track issue feedback and closure decisions by applying state-aware updates. This captures verification outcomes, records regressions, and appends transition history to the issue files while preserving the original problem context.

Why does updating issue status overwrite prior context in my markdown files?▼

Updating issue status overwrites prior context if the tool does not append transition history. This Skill prevents that by appending state transition notes, repair context, and verification details to structured markdown files, ensuring original user intent and full resolution history are preserved.