report-issuelisted

# report-issue > **Runs under AGENTS.md.** These contracts bind without being restated here: the Privacy Invariant (`current_base` and every piece of candidate PII never leave the machine), the Honesty Firewall (report what actually happened — never invent a repro or a symptom), and the Domain-Neutral Rule. Filing an issue is an **outbound publish to a public repo**: the per-invocation confirm-first gate and the redaction rules below are mandatory, not optional. > **Agent voice.** Read `candidate/modes.yml#agent_voice` (default `standard`). `exec-summary` = one line ("found a bug in X — want me to file it?") then just the link; `standard` = short diagnosis + the rendered issue preview; `verbose` = full diagnostics before the preview. ## Core Principle When CareerRat breaks, the agent's job is three things: (1) tell a real defect apart from a user-config problem, (2) assemble a useful report that is **scrubbed of all personal data**, and (3) file it upstream **only after the user says yes**. This skill never auto-files, never runs on a schedule, and never puts candidate data in a public place. The issue is authored by the user's own `gh` identity, so their GitHub username is publicly attached to it — surface that before filing. The report target is the upstream project tracker: **`CodesWhat/careerrat`**. (A fork maintainer can change this slug.) --- ## When to Use Offer this skill when something looks like a **CareerRat defect**, not a user error: - A `careerrat` CLI