菜单
Phase-1 repo reconnaissance as a standalone skill: stack detection, relevant files, validation commands from repo evidence, workflow hints, and risk flags. Use inside /scout, /ks-conductor pre-flight, or any read-only discovery before planning or implementation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to the knowledge-synthesizer subagent. Use when asked to mine prior chats, maintain AGENTS.md, update learned preferences, or run the continual-learning loop.
Security-focused review of code diffs and PRs with surface classification and Semgrep on changed files. Use when reviewing pull requests, branch diffs, or validating security regressions before merge.
Live Notion session log (L4b) — create, incremental updates during work, finalize on CLOSE. Works on any Cursor project workspace.
Bootstrap a new project with Cursor-ready configuration: AGENTS.md, per-project .cursor/rules/project-conventions.mdc, and optional memory_bank/ scaffold. Use at project initialization, when starting a new repo, or when the user says "set up Cursor for this project" / "bootstrap this project" / "init project config".
Validates phase outputs before advancing the SDLC. Defines expected artifacts per phase (intake, scout, plan, critic, build, test, review, document, close) and produces a clear PASS / CONDITIONAL / BLOCK verdict with gaps. Use at orchestrator or command phase boundaries, before expensive work, or when the user asks to verify a gate or "are we ready to proceed".
Runs Semgrep static analysis security audits with scoped rulesets and structured findings. Use for security scans, vulnerability audits, or when touching auth, secrets, SQL, or user input boundaries.
| name | repo-discovery |
| description | Phase-1 repo reconnaissance as a standalone skill: stack detection, relevant files, validation commands from repo evidence, workflow hints, and risk flags. Use inside /scout, /ks-conductor pre-flight, or any read-only discovery before planning or implementation. |
On-demand loading: Read this skill only when the task clearly matches the description above. Do not load for unrelated work.
Execute minimal effective reconnaissance to map the real implementation surface: stack, boundaries, commands, tests, and risks—without editing files or designing the solution.
/scout Phase 1 (read this skill and align output with scout report format).Not for: Full onboarding doc for new team members — use codebase-onboarding (parallel explore + synthesized guide).
/ks-conductor when skipping a full /scout invocation but discovery is still required./build-full pre-flight when the execution pack lacks verified commands or file paths.scout-YYYY-MM-DD-*.md for the same task.package.json, pyproject.toml, Gemfile, go.mod, etc.), lockfiles, CI, and directory layout—infer framework, package manager, monorepo layout..cursor/rules, /docs/, migrations folder, security-sensitive areas (auth, payments, uploads).Produce bullets or tables suitable for pasting into:
classification, confidence, workflow_type, next_command (see phase-handoff / /scout artifact schema)./scout must still run Phase 0 (user-devcontext, optional brainstorming) and Phase 2 (user-Sequential Thinking when triggered) unless this skill is invoked only as a sub-step inside scout.explore for large unknown repos when parallel speed helps.