← ClaudeAtlas

scrub-and-open-issuelisted

Scrub PII and company identifiers from a GitHub issue draft, then file it via gh as the repo owner, not the work account. Triggers on: scrub PII, file as repo owner, not the work account, open a scrubbed issue.
sblattj/agent-chandlery · ★ 0 · Code & Development · score 72
Install: claude install-skill sblattj/agent-chandlery
## More triggers Triggers on: "open a scrubbed issue", "file a sanitized bug/feature", "open an issue but scrub PII", "file this as the repo owner not my company account", "redact company info and open an issue", "report this upstream without leaking work stuff", "pii scrub please", "anonymize the speaker table". Also: working inside a company/org repo and hit a limitation of a tool or framework you want to report upstream; "open an anonymous issue on <owner/repo>"; "post replay evidence on the issue"; push or open a PR on a personal repo as its owner. # Scrub PII and open a GitHub issue as the repo owner Use this when you are working inside a company/org repo (for example `my-org/acme-api`) and want to file a bug or feature request against a **separate** tool/framework repo (typically one the user owns under their personal account, `<owner>` below) without leaking any employer, teammate, product, or personal identifiers, and without the company GitHub account (whatever login is on the local blocked-authors list) authoring it. The idea: two GitHub accounts live side by side in `gh` (a personal one that owns your tools, a work one that is usually active). Anything filed, commented or pushed on a personal repo goes out as the personal owner, scrubbed of work details, and the work account never authors it. ## The two hard rules (do not skip) 1. **Author = repo owner, or no issue.** The gh account that creates the issue MUST equal the target repo's owner (for user-owned re