skills.rest
cirne
cirneCOMMUNITY
Explore all skills by this author →
Website𝕏@sweetlewGitHub

process-feedback

Convert feedback markdown files into structured bug reports or code fixes.

Updated Aug 23, 2026
Search Tags:#automation#workflow#feedback#documentation#opportunity#issue-tracking#bug
One-click install
npx skills add https://github.com/cirne/zmail --skill process-feedback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: process-feedback
Source: https://github.com/cirne/zmail/tree/main/.cursor/skills/process-feedback
Command: npx skills add https://github.com/cirne/zmail --skill process-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow converts incoming feedback into structured items for project tracking, enabling teams to decide between documenting issues or implementing fixes.

Core Features & Use Cases

  • Idempotent processing: safely processes feedback multiple times without duplicating records.
  • Workflow orchestration: reads feedback from ../ztest/feedback, checks existing bugs/opportunities, updates trackers, and moves processed files to submitted.
  • Audit-friendly: preserves an audit trail with updates to docs/feedback-processed.md and related indices.

Quick Start

Place a feedback file in ../ztest/feedback and run the processor to classify it into a bug or opportunity.

Frequently Asked Questions about process-feedback

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

FAQPage Schema
How do I automatically convert markdown feedback files into structured bug reports?▼

To convert markdown feedback into structured bug reports, this workflow reads feedback files, classifies them as bugs or opportunities, and updates trackers. It applies idempotency checks to avoid duplicates and moves processed files to a submitted archive.

What is idempotent feedback processing and why is it needed for issue tracking?▼

Idempotent feedback processing means safely running the workflow multiple times on the same input without creating duplicate bugs or opportunities in your tracker. It ensures safe handling of duplicates and maintains an audit trail.

How do I start automating a feedback workflow that categorizes issues and opportunities?▼

To start automating your feedback workflow, place a markdown feedback file in the designated input directory and run the processor. It classifies the content into a bug or opportunity, updates tracking indices, and archives the processed file.

Does this feedback processing workflow support multiple projects and maintain an audit trail?▼

Yes, this workflow supports feedback flows across multiple projects and maintains an audit trail. It preserves records by updating a processed feedback document and related indices when generating bugs or opportunities.

What happens to feedback files after they are processed into bugs or code fixes?▼

After feedback files are processed into bugs or fixes, they are moved to a submitted archive. This workflow orchestration prevents reprocessing and maintains a clean input directory for new incoming feedback.

Related Skills

Explore More Product & Management Skills→
DavidROliverBADavidROliverBA
49

inbox-watcher

Monitor directories for unprocessed files and suggest handling skills.

Community
Intermediate
saitarrunsaitarrun
4

triage

Enforce structured issue triage workflows with defined roles and states.

Community
Intermediate
hwj123hwjhwj123hwj
4

setup-matt-pocock-skills

Automate issue tracker, triage label, and domain documentation setup for engineering projects.

Community
Advanced
chtughachtugha

review-crate

Audits Rust crates for vulnerabilities, bugs, and code issues using Cargo tools and manual review processes.

Community
Advanced