github-triage

To generate read-only triage reports for GitHub issues and PRs, this Skill fetches all open items using only GET requests and writes per-item analysis with evidence-backed permalinks to local files, ensuring the repository state remains completely unchanged.

Yes, you can analyze all open GitHub issues without modifying the repository state by enforcing a zero-action policy that restricts operations to GET reads and local report writes, preventing any mutations to the live GitHub repository.

To get evidence-backed permalinks for GitHub issue triage, the analysis process captures commit SHA permalinks for every open item, embedding them directly into structured local reports for full traceability and decision support.

GitHub triage report outputs are stored locally under the /tmp/{datetime}/ directory path, organizing filenames by timestamp to ensure traceability without ever writing back to the GitHub repository.

The best way to perform a non-mutating GitHub pull request analysis is to use a zero-action workflow that collects every open PR via read-only GET requests and generates structured local reports containing commit SHA permalinks for evidence.