Update issue status records and verification history in structured markdown files.
npx skills add https://github.com/cc-claws/cc-code --skill issue-verify-cc-claws
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
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.
Tell the assistant which issue to update and what outcome you want, then share any verification details, symptoms, or status change you want recorded.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
N0K0Generate structured specification documents as GitHub Issues or local markdown files.
AbyssCNAnalyze git history to generate engineering retrospective reports.
workinprogress-aiSynchronize roadmap Markdown files with GitHub issue and pull request states.
withzombiesAutomate bug fixing from issue creation through regression testing and closure.
