fix: require user approval before posting skill feedback
Summary
- Cloudflare updated its skill feedback guidelines across multiple reference repositories to mandate explicit user approval before posting issues.
- The changes explicitly forbid including sensitive information like credentials, API tokens, account IDs, personal data, and internal URLs in public feedback.
- A explicit review step requires showing the user the exact title and body and receiving a yes/no response before any GitHub issue creation.
- New instructions specify how to handle draft revisions and ensure proper manual submission fallbacks if automated CLI creation fails.
Why it matters
Enforcing strict user review and data redaction policies for AI-driven skill feedback prevents accidental leaks of sensitive credentials and internal enterprise data into public repositories.