Triage Github Issue
Productivitytriage-github-issueTriage Github Issue is an Agent Skill for productivity published in the salesforce/cloudsplaining repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Take a GitHub issue or proposal, research it against this repo, frame 2-3 options, and help the user decide — then emit a plan and optionally launch the mega-pipeline. This skill should be used to turn an incoming proposal (e.g. a pathfinding.cloud privesc path) into a decided, planned, ready-to-execute change.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/salesforce/cloudsplaining/blob/HEAD/.claude/skills/triage-github-issue/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/triage-github-issue, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Triage GitHub Issue
Turn a proposal into a decision plus a plan, then hand off to execution.
When to use
- A GitHub issue proposes a change (e.g. "add these pathfinding.cloud techniques").
- The user wants help deciding scope/approach before building.
Workflow
- Fetch the issue.
gh issue view <n> --json title,body,labels,comments(or accept the proposal text directly). - Research context. Read the relevant code/docs. For privesc proposals:
cloudsplaining/shared/constants.py,research/pathfinding-cloud/INTEGRATION-ANALYSIS.md, andresearch/pathfinding-cloud/proposed-privilege-escalation-methods.py. Determine what is already covered vs new (the analysis already classifies this). - Frame options. Use the
superpowers:brainstormingskill to develop 2-3 concrete approaches with trade-offs (which techniques to onboard first, how to handle variant supersets and noisy single-action methods, whether to refresh fixtures now). - Decide. Use
AskUserQuestionfor each genuine decision; record the choices. - Plan. Write a short decision summary + step plan to the configured plans directory (
docs/plans/). - Hand off. Offer to run the
mega-pipelineskill with the decided technique list, or stop at the plan.
Notes
- This skill decides and plans; it does not implement. Implementation is
mega-pipeline→onboard-privesc-technique. - Keep decisions frontloaded so
mega-pipelinecan run with minimal gates.