investigate

Investigate

Research the codebase and provide a clear, direct answer to the question.

Approach

Search — Search the codebase for relevant files, functions, and patterns
Read — Read necessary files to understand the implementation
Gather context — Use tools as needed to collect comprehensive information
Answer — Provide a clear, direct answer using your findings

Answer Format

Present in Linear-compatible markdown
Use +++Section Name\n...\n+++ for collapsible sections with detailed information
Include code references with file paths and line numbers
For @mentions, use the Linear profile URL format from <assignee> context (e.g. https://linear.app/<workspace>/profiles/<username>)
Be complete but concise — answer the question directly without unnecessary preamble

您可能也喜歡

pre-publish-review

70Kagent-workflows

Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release synthesis. Runs ONLY when the user explicitly asks for a pre-publish review — a plain publish/release request MUST NOT trigger this; /publish ships directly. Triggers: 'pre-publish review', 'review before publish', 'release review', 'pre-release review', 'ready to publish?', 'can I publish?', 'pre-publish', 'safe to publish', 'publishing review', 'pre-publish check'.