Skip to content
cccskills
FreePublished on GitHub

investigate-and-plan

Investigate errors, incidents, or product ideas using both internet research and repo-wide codebase research, then propose a concrete changeset plan with clarifying questions before any implementation. Use when a user asks to investigate, root-cause, or plan changes, or when an Issue or PR is referenced and needs a plan.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Investigate And Plan

Claude Code mirror of .codex/skills/investigate-and-plan/SKILL.md.

Overview

Investigate the request, research external sources and the codebase, and produce a plan for a changeset before writing code. Ask open clarifying questions with defaults, then implement only after the plan is agreed.

Workflow

1) Confirm scope and gather context

  • Identify the exact error, feature idea, or decision to investigate.
  • If a PR or Issue is referenced, use the GitHub CLI to fetch details and comments.
  • List the codebase areas to inspect, including backend, frontend, bot, infra, scripts, tests, docs, and configuration.

2) Research

  • Use WebSearch / WebFetch for internet research, then cite sources for any external facts.
  • Search the codebase broadly with targeted deep dives into relevant subsystems.
  • Capture findings, constraints, and risks, including any existing TODOs or comments.

3) Propose the changeset

  • Provide a concrete plan with files to touch, key edits, data migrations, and test updates.
  • Call out assumptions and viable alternatives.
  • Ask open questions that block implementation, and provide defaults for each question.
  • Do not write code yet.

4) Implement after agreement

  • Wait for the plan to be accepted or adjusted.
  • Implement the agreed changes, keeping the scope aligned to the plan.
  • If new information changes the plan, pause and confirm the update.

5) Validate

  • Run the repo check command. Common gates: yarn lint:check, yarn test, yarn build:all, and yarn docs:check when docs changed. Use yarn test:e2e / yarn test:visual for UI changes.
  • Report command outcomes and any remaining gaps.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Analyze Chronote product adoption with PostHog and Langfuse, including active users, meetings, feature usage, AI telemetry, and privacy-safe resolution of active Discord guild IDs to live server names.

The English summary is being prepared. Showing the original description.

Chronote-gg/Chronote4Updated Oct 23, 2026

Use when a change affects user-visible behavior at docs.chronote.gg and needs public documentation. Covers where docs live (apps/docs-site vs docs/), authoring checklist, yarn docs:check, and Algolia config. Trigger when the user mentions docs, release notes, what's-new, or user-facing PR changes.

The English summary is being prepared. Showing the original description.

Chronote-gg/Chronote4Updated Oct 23, 2026

Query aggregate Langfuse cost, volume, latency, and model telemetry efficiently with Metrics API v2. Use for dashboards, rollout checks, usage summaries, and cost or latency comparisons; use Observations API v2 instead when individual rows are actually required.

The English summary is being prepared. Showing the original description.

Chronote-gg/Chronote4Updated Oct 23, 2026

Configure and debug MCP servers for OpenCode, Codex CLI, and Claude Code, including auth headers, scope, and validation checks. Use when MCP tools fail to connect or when adding a new MCP server.

The English summary is being prepared. Showing the original description.

Chronote-gg/Chronote4Updated Oct 23, 2026

Configure and debug MCP servers for Claude Code, OpenCode, and Codex CLI, including auth headers, scope, and validation checks. Use when MCP tools fail to connect, when an MCP server returns 401/404/HTML, or when adding a new MCP server to this repo.

The English summary is being prepared. Showing the original description.

Chronote-gg/Chronote4Updated Oct 23, 2026

Use every time you push a commit to an active pull request, to verify the PR is truly stable before reporting merge readiness. Covers the post-push wait window, AI review audit (Copilot/Greptile/Codex), and the gh commands to snapshot PR state. Trigger on "I pushed" or "is the PR ready to merge".

The English summary is being prepared. Showing the original description.

Chronote-gg/Chronote4Updated Oct 23, 2026

See all skills by Chronote-gg

Report a problem with this skill