メニュー
Explore repository structure, map dependencies, and surface conventions before making changes. Use when onboarding to a new repo, investigating unfamiliar code, or preparing context for a review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Summarize git history, staged diffs, or PR changes into clear, human-readable summaries grouped by theme.
Generate Conventional Commits-compliant commit messages from staged changes or a description of work done.
Build marketing-grade code displays for the Musher marketing site -- split-panel code-then-output layouts, CSS-only syntax highlighting, tabbed views, and terminal chrome. Use when implementing IA Section 3 (Mechanism), building code blocks, creating terminal demos, highlighting YAML/CLI output, or adding copy buttons to code. Triggered by: code display, code block, syntax highlighting, code-then-output, split panel code, terminal chrome, YAML highlight, CLI output, code snippet, tabbed code, multi-language code, mechanism section code, bundle yaml, pipeline yaml, marketing code.
Scaffold marketing page sections from IA definitions into Svelte 5 components. Use when building section components from the Information Architecture, translating archetypes to markup, mapping content slots to elements, or creating section scaffolds. Triggered by: scaffold section, build section, IA to component, section component, hero section, mechanism section, value grid, proof block, community block, CTA block, social proof bar, content slot, archetype component, layout pattern, section scaffold, marketing component.
Analyze CSV data by computing aggregations, filtering rows, and generating readable summaries. Use when working with tabular data files in a container environment where the agent creates and manipulates files directly.
Ensure local development environments match CI/CD environments for consistent behavior including shared version sources, devcontainer reuse in CI, reproducible dependency installation, environment variable parity, Docker image sharing, and lock file enforcement. Use when diagnosing works-on-my-machine issues, designing CI pipelines that mirror local dev, or auditing environment parity. Triggered by: CI alignment, CI environment, works on my machine, CI parity, environment parity, CI local match, GitHub Actions, CI pipeline, CI docker, reproducible builds, lock file, frozen lockfile.
| name | researching-repos |
| description | Explore repository structure, map dependencies, and surface conventions before making changes. Use when onboarding to a new repo, investigating unfamiliar code, or preparing context for a review. |
Systematically explore a repository to build the context needed for effective code review or contribution.
Identify the stack — read root config files (package.json, pyproject.toml, go.mod) to determine languages, frameworks, and dependency versions.
Map the structure — walk the top-level directories and identify their roles (source, tests, config, docs, scripts, CI).
Find entry points — locate main files, route registrations, CLI entrypoints, or event handlers that anchor the request/data flow.
Trace dependencies — follow imports from entry points to understand which modules depend on which, and where shared types or utilities live.
Discover conventions — read 2-3 representative source files to learn naming patterns, error handling style, test organization, and commit message format.
Note pain points — flag areas with high complexity, outdated dependencies, missing tests, or inconsistent patterns.
Produce a concise summary covering:
