feedbacklisted

# Feedback — Community Contribution Loop ## Task $ARGUMENTS ## Purpose Help users contribute back to the SDLC wizard: bug reports, feature requests, pattern sharing, and SDLC improvements. Privacy-first — never scan without explicit permission. ## Privacy & Permission (MANDATORY) **NEVER scan the user's repo without explicit consent.** Always ask first: > "I can scan your SDLC setup to identify what you've customized vs wizard defaults. This helps me create a more specific report. May I scan? (Only file names and SDLC config are read — no source code, secrets, or business logic.)" **What IS scanned (with permission):** - SDLC.md, TESTING.md, CLAUDE.md structure (not content details) - Hook file names and which hooks are active - Skill names and which skills exist - .claude/settings.json hook configuration (not allowedTools or secrets) **What is NEVER scanned:** - Source code files - .env files, secrets, credentials - Business logic or proprietary code - Git history or commit messages ## Feedback Types ### Bug Report 1. Ask user to describe the issue 2. With permission, check which wizard version is installed (`SDLC.md` metadata) 3. Check if hooks are properly configured 4. Create a GitHub issue with reproduction steps ### Feature Request 1. Ask user what they want 2. With permission, check if a similar capability already exists in their setup 3. Create a GitHub issue with the request and context ### Pattern Sharing 1. Ask user what pattern they've discovered (cust