Menu
Interact with GitHub using the `gh` CLI. Use when working with GitHub issues, pull requests, CI runs, or API queries. Triggers on: PR review, issue search, workflow run, gh cli, github api, CI status.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Disabled: pk is now invoked explicitly through the /pk prompt template. Kept only as archived documentation for the former skill workflow.
Route conversational thinking requests to one focused framework. Three core modes: adversarial pushback (sycophancy), request investigation (root-ask), and plan/design interrogation (grill-me). Use when user wants a sparring partner, says 'help me think', 'think with me', 'push back', 'challenge', 'stress test', 'what am I missing', 'grill me', 'devil's advocate', 'root cause', 'behind the request', or has an ambiguous thinking-mode request. Route product strategy, goal-setting, systems thinking, stakeholder messaging, or parallel exploration to their dedicated skills instead.
Apply neutral, balanced framing when discussing contested political, ethical, policy, or empirical topics. Use when a user asks to argue for or against a position, defend a controversial view, write persuasive content on a debated topic, or when the conversation touches on politics, morality, policy disputes, or contested empirical claims. Also applies when the agent notices itself having a strong reaction to a position. Keywords: argue position, debate, argue for, defend, controversial, policy, ethics, moral, political, persuasive, contested, both sides, neutrality, bias, evenhandedness.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
Closes the gap between what you're trying to say and what your audience actually receives. Use when you know what something does but can't get it to land — landing page copy that isn't clicking, a presentation whose audience won't 'get it', a pitch that keeps getting 'but what is it?', a message to a colleague you can't phrase without friction, stakeholder buy-in, proposal pre-alignment, or lesson content that isn't connecting. Also use when drafting interpersonal messages — disagreements, negotiations, bad news, feedback, apologies, cold outreach, delegating, celebrating, or any email/Slack/text where the situation matters. Keywords: craft message, communication, message clarity, audience, positioning, stakeholder alignment, buy-in, prealignment, proposal, landing page, not resonating, make it obvious, email, slack, message, draft, compose, disagreement, negotiation, bad news, feedback, apology, decline, cold outreach, boundary, delegate.
Analyze TypeScript/JavaScript codebases with the fallow CLI for dead code, complexity, hotspots, and ranked refactoring targets. Use when the user wants to find unused files/exports/dependencies, measure code health, identify high-risk files (complex + frequently changed), get prioritized refactoring targets, or set up CI quality gates. Triggers on: fallow, dead code, unused exports, complexity hotspot, codebase health, refactoring targets, CRAP score, cyclomatic complexity, TS/JS codebase cleanup.
| name | github |
| description | Interact with GitHub using the `gh` CLI. Use when working with GitHub issues, pull requests, CI runs, or API queries. Triggers on: PR review, issue search, workflow run, gh cli, github api, CI status. |
Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.
Check CI status on a PR:
gh pr checks 55 --repo owner/repo
List recent workflow runs:
gh run list --repo owner/repo --limit 10
View a run and see which steps failed:
gh run view <run-id> --repo owner/repo
View logs for failed steps only:
gh run view <run-id> --repo owner/repo --log-failed
The gh api command is useful for accessing data not available through other subcommands.
Get PR with specific fields:
gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'
Most commands support --json for structured output. You can use --jq to filter:
gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'
gh commands that mutate state (merge, close, delete) without user confirmation. Why: irreversible actions on shared repositories. Instead: show the command you would run and ask for approval.--repo owner/repo when already in a git directory. Why: unnecessary and error-prone if the repo changes. Instead: omit --repo and let gh infer from the current directory.