kit-feedback

To capture and sanitize project learnings, this Skill scans your host project for cross-project lessons, template improvements, and anti-patterns, then stages them as kit-ready candidates. It applies a full sanitization pipeline before writing results to dev_docs/kit-feedback.

Project feedback export works by staging captured improvement candidates and writing them into a portable .kit-feedback.json file. This format is ready for submission to kit maintainers via GitHub PR or direct file share.

The best way to document anti-patterns is using the interactive candidate creation mode. It captures project-side improvement signals and sanitizes them into structured candidates, storing them with pending or exported statuses for manual review.

Yes, you can use this workflow to track statuses. It supports pending and exported statuses for captured candidates, allowing you to manage the pipeline from initial signal discovery to final JSON export.

No specific dependencies are required to run the kit feedback workflow. The Skill operates independently within your project directory to scan for insights and generate the exportable feedback file.

Project feedback needs sanitization to ensure cross-project lessons and template improvements are safe and structured for kit integration. The sanitization pipeline processes raw signals into clean, kit-ready candidates suitable for export.