Menu
Investigate a GitHub bug ticket by fetching PII from the go/github-pii doc and suggesting BQ investigation queries.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Investigate a stable counts validation failure for a state supervision or incarceration period table by identifying which fields changed and why. Use when a stable counts validation is failing or has recently failed for a state entity (e.g. "why is the NC stable counts failing", "investigate stable counts for US_ID supervision periods", "dig into the stable counts failure for supervision periods").
Create a GitHub PR for the current branch with auto-generated description. Use when the user asks to create a pull request, open a PR, or put up changes for review.
Post a validation comment to a GitHub PR or issue using the standard format. Use when the user asks to post a comment to a PR or issue, post sandbox or ingest validation results, share validation findings on a PR or ticket, or anything similar that involves posting validation results as a GitHub comment.
Add a new field to opportunity configs in the workflows admin panel. Use when asked to add a new config field, property, or attribute to the workflows opportunity configuration system.
Use this skill when a user wants to structure BigQuery views into the standard Pollen view pattern. All Pollen analysis is in the research/notebooks/policy folder -- do not apply this skill outside that folder. Triggers include: "structure my views", "create view files", "pull views from my notebook", "set up the view folder structure", "make my SQL into view builders", or any request to convert notebook SQL or .sql files into the SimpleBigQueryViewBuilder pattern used by policy analysis work.
File issues and tasks for the pulse-data repository. Use when the user asks to file, create, or track issues, tasks, tickets, or TODOs. Defaults to filing in Linear (which two-way-syncs to GitHub) and lets you set Linear-specific fields like project and milestone; falls back to filing directly in GitHub when Linear is unavailable. Handles templates, labels, team/project/milestone assignment, parent linking, and in-code TODO references.
| name | investigate-pg-ticket |
| description | Investigate a GitHub bug ticket by fetching PII from the go/github-pii doc and suggesting BQ investigation queries. |
This skill takes a GitHub issue URL from pulse-data (where PG tickets are
now filed) or recidiviz-dashboards (the legacy source — tickets filed there
before the cutover to pulse-data are still supported until they've been
worked through; TODO(#84434) tracks dropping recidiviz-dashboards support),
fetches the ticket details, retrieves associated PII from the shared Google Doc,
and suggests specific BigQuery investigation paths based on the ticket context.
Extract the repo and issue number from the URL, then fetch the ticket:
gh issue view <NUMBER> --repo <ORG>/<REPO> --json title,body,labels,comments
Use the Google Docs API with gcloud credentials to retrieve PII details. The
parsing script is stored at
.claude/skills/investigate-pg-ticket/parse_github_pii_doc.py.
The parser script detects API errors (e.g. expired auth tokens) and exits with a
clear error message. If it reports an auth error, ask the user to run
gcloud auth login and retry.
ACCESS_TOKEN=$(gcloud auth print-access-token) && \
curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
"https://docs.googleapis.com/v1/documents/1hYq--Xw6D5Lu96pSFVGeNu9AuxMNtB5F4ltI2VE9FZs" \
| python3 .claude/skills/investigate-pg-ticket/parse_github_pii_doc.py <ISSUE_NUMBER>
Replace <ISSUE_NUMBER> with the actual issue number (e.g., 12097).
@.claude/skills/investigate-pg-ticket/extract-key-details.md
If you're not confident which one is the right match, ASK the user (use AskUserQuestion tool) with the candidates you found as options.
@.claude/skills/investigate-pg-ticket/look-up-person-ids.md
Follow the applicable diagnosis path depending on the product area.
For Workflows (also referred to as Opportunities — they're the same product area):
@.claude/skills/investigate-pg-ticket/diagnose-workflows.md
For Tasks:
@.claude/skills/investigate-pg-ticket/diagnose-tasks.md
For Insights / Supervision Homepage (SHP):
@.claude/skills/investigate-pg-ticket/diagnose-insights.md
If the issue is not relevant to any of these three product areas: Stop and inform the user that there are no specific diagnosis instructions for this product area, rather than trying to fit the issue into one of the above buckets. The user can decide how to proceed (e.g., investigate manually).
@.claude/skills/investigate-pg-ticket/present-diagnosis-results.md
recidiviz-123 for investigation unless the user specifies
otherwise1hYq--Xw6D5Lu96pSFVGeNu9AuxMNtB5F4ltI2VE9FZsgcloud auth login first