babysit-pr
Use after a pull request is open to watch its CI and review-bot comments until it is ready. Fixes real findings, replies with a…
@greenfield-incInstall SkillAgent Orchestration
Skill
/investigate
Investigate a bug or broken behavior through hypothesis-driven root cause analysis and report what is wrong without jumping straight to a fix. Use when something is failing or behaving unexpectedly.
Claude Code
$ npx -y skills add greenfield-inc/Pane --skill investigate --agent claude-code
Codex
$ npx skills add greenfield-inc/Pane --skill investigate -a codex -y
Cursor
$ npx skills add greenfield-inc/Pane --skill investigate -a cursor -y
Gemini CLI
$ npx skills add greenfield-inc/Pane --skill investigate -a gemini-cli -y
GitHub Copilot
$ npx skills add greenfield-inc/Pane --skill investigate -a github-copilot -y
OpenCode
$ npx skills add greenfield-inc/Pane --skill investigate -a opencode -y
Windsurf
$ npx skills add greenfield-inc/Pane --skill investigate -a windsurf -y
SKILL.md
investigate.SKILL.mdname: investigate description: Investigate a bug or broken behavior through hypothesis-driven root cause analysis and report what is wrong without jumping straight to a fix. Use when something is failing or behaving unexpectedly.
Investigate
Find the root cause before proposing a fix.
Rules:
- Do not make code changes unless the user explicitly approves diagnostic logging.
- Do not guess. Support every conclusion with evidence from code, logs, or commands.
Workflow: 1. Clarify expected behavior, observed behavior, and reproduction steps if missing. 2. Classify the bug type early: compile, logic, race, state, integration, environment, or UI. 3. Write 3-5 ranked hypotheses before reading deeply. 4. Test those hypotheses by tracing the relevant code and recent history. 5. Compare broken and working paths when possible. 6. If the cause is still unclear, propose targeted logging and explain exactly why. 7. Report the root cause, confidence level, affected files, likely introduction point, and what needs to change.
Red flags:
- proposing a fix before confirming the cause
- pursuing the same failed theory repeatedly
- analyzing code unrelated to the symptoms
Stats
616
Stars
236
Forks
Active
Maintenance
TypeScript
Language
Last commit
Created
Added
59739 skills4 agents
Stars on GitHub
Momentum
- stars in total
- 597
Other skills on pane.
@greenfield-incInstall Skillbrief
Use when a problem, idea, or change of intent is worth capturing as a long-form page, or the person asks to write it up. Never…
@greenfield-incInstall Skillbug-intake
Use when the person reports broken behaviour or starts a session to file a bug. Reproduces and reports. Never fixes.
@greenfield-incInstall Skillcodebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening…
@greenfield-incInstall Skillcodebase-explorer
Explore the codebase to locate files, trace behavior, and document existing patterns with precise file references. Use when the…
@greenfield-incInstall Skillcold-read
Give a fresh agent something to walk through with zero context - a PR body, a landing page, a document, a process, instructions,…
@greenfield-incInstall SkillMore skills from other plugins.
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by…
@paperclipaiInstall Skilladr-create
Create a new Architecture Decision Record with sequential numbering and AgentDB registration
@ruvnetInstall SkillQuestions about investigate.
- Which coding agents can use investigate?
- investigate installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.