parallel-investigator
Investigate two separate areas of the codebase simultaneously and combine findings into a comparison report. Use when you need research on two independent topics at once, want to compare two subsystems, or need to understand how two components relate to each other.
- License 许可
- MIT
- 最近更新
- 2026-05-15
- Stars
- ★ 13
- Forks
- 1
01 前言 Front Matter
- name
- parallel-investigator
- title
- parallel-investigator
- description
- Investigate two separate areas of the codebase simultaneously and combine findings into a comparison report. Use when you need research on two independent topics at once, want to compare two subsystems, or need to understand how two components relate to each other.
- argument-hint
- [topic-1] [topic-2]
- disable-model-invocation
- true
02 资源文件 1
- 参考文档agents/openai.yaml94 B
03 SKILL.md 正文
Investigate these two topics in parallel using separate Explore subagents:
- Topic 1: $0
- Topic 2: $1
Instructions
-
Spawn two Explore subagents simultaneously — one per topic. Give each a self-contained research prompt that includes:
- The specific topic to investigate
- Instructions to search broadly (Grep, Glob) before reading files deeply
- Instructions to produce a structured report: key files, how it works, notable patterns
Do not run the subagents sequentially. Start both at the same time.
-
Wait for both subagents to return their results.
-
Combine the findings into a single comparison report with these sections:
Topic 1 findings — summary of what the first subagent found
Topic 2 findings — summary of what the second subagent found
Similarities — patterns, libraries, approaches, or design decisions shared between the two topics
Differences — how they diverge: in scale, in architecture, in data model, in error handling, or in how they are tested
Recommendation — if the user is trying to make a decision (e.g., which approach to follow, which subsystem to extend), give a direct recommendation with reasoning. If the topics are purely informational (e.g., understanding two independent systems), omit this section.
Note on architecture
This skill does not use context: fork — it runs inline in your main conversation. This is intentional: a forked skill cannot spawn additional subagents, so any skill that needs to orchestrate multiple workers must run in the main context and delegate the worker tasks from there. The main conversation is the orchestrator; the Explore subagents are the workers.
04 同仓库更多 Skills
tag-version
Bump the package version and create an annotated git tag. Accepts a semantic version number (1.2.0) or a bump type (patch, minor, major). Does not push — use the publish skill to push. Use as part of a release workflow.
release
Run the complete release workflow: changelog entry, version bump, git tag, and GitHub release. Invokes changelog-entry, tag-version, and publish in sequence. Use when releasing a new version of the project.
publish
Push the current branch and all tags to origin, then create a GitHub release using the latest tag and its CHANGELOG.md entry. Use after tag-version to complete a release.
changelog-entry
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
auto-format-on-edit
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
code-quality-audit
Run a comprehensive code quality audit covering security, performance, and maintainability. Use for quarterly audits, pre-release reviews, or when onboarding to a large codebase.