contributor-mode-onlisted

Use this skill when the user wants to opt in to iEvo 'contributor mode' for this project — trigger words "turn on contributor mode", "enable contributor mode", "I am a contributor", "share more diagnostics with feedback", "widen feedback payload". Enables a project-local, off-by-default consent flag (`.ievo/contributor.flag`) that widens what `/ievo:feedback` MAY offer to attach to a filed report: the environment context it already collects for every report, plus — only when available — the existing scrubbed tool-failure/permission-denial capture stream from `/ievo:evo-auto-enable`. The existing per-report Submit/Cancel confirmation in `/ievo:feedback` is unchanged; this flag only widens the attachment OPTIONS offered and never auto-posts. Does NOT add a session-transcript export or standing consent to skip the per-report confirmation — both are separate, unbuilt proposals (see `## Scope` below).
ievo-ai/skills · ★ 0 · Data & Documents · score 72

Install: claude install-skill ievo-ai/skills

# Contributor Mode On — opt in to widened `/ievo:feedback` diagnostics Turns on a project-local consent flag, `.ievo/contributor.flag`, that widens what `/ievo:feedback` may OFFER to attach to a filed report. Off by default; disabled again with `/ievo:contributor-mode-off`. ## Scope (read before enabling) — what this is, and is not This is **Phase 1** of a two-phase proposal (`ievo-ai/skills#448`). Only Phase 1 is built. Read both lists before enabling. **What turning this ON actually changes:** - `/ievo:feedback` gains one additional, always-optional attachment it may offer at report time: the existing **scrubbed tool-failure/permission-denial capture stream** — the same records `/ievo:evo-auto-enable`'s `signal: corrections+failures` already accumulates under `.ievo/evolution-candidates/`, each one already redacted by `scrub.mjs` before it ever touched disk — redaction, not removal: a record still carries the failing call's own input arguments, so read Step 2's consent manifest below for exactly what that includes. Without this flag, `/ievo:feedback` never offers that stream, even if it has candidates. - The environment context `/ievo:feedback` already collects for **every** report (client, versions, OS, project stack) is unaffected — that was already always included and this flag changes nothing about it. - The existing per-report **Submit / Cancel confirmation** (`/ievo:feedback` Step 5) is completely unchanged: you still see the full title + b