search-before-acting
Search for what already does an ask before logging, planning, delegating, or building it, then report what exists in four points. When the role-level job is already authorized, continue that job. Use when a user asks for new or changed behavior, a tool, a check, a workflow, a report, a tracker entry, or a plan, and before writing a brief for a worker.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- search-before-acting
- description
- Search for what already does an ask before logging, planning, delegating, or building it, then report what exists in four points. When the role-level job is already authorized, continue that job. Use when a user asks for new or changed behavior, a tool, a check, a workflow, a report, a tracker entry, or a plan, and before writing a brief for a worker.
02 资源文件 5
- 参考文档playbooks/build.md1.4 KB
- 参考文档playbooks/delegate.md724 B
- 参考文档playbooks/plan-or-log.md893 B
- 参考文档references/report-shape.md1.1 KB
- 参考文档references/search-places.md2.0 KB
03 SKILL.md 正文
Search before acting
The user should hear about work that already does their ask before anyone duplicates it. Search first, report what you find, and let the user decide what to add.
Steps
- Restate the ask as the outcome the user wants, in their words.
- Search every place in
references/search-places.mdthat this session can reach. Note each place you could not reach. - Sort each hit as full, partial, or related. A hit is full when it already produces the outcome from step 1.
- When any hit is full or partial, send the four-point report from
references/report-shape.md. When the role-level job is already authorized, continue that job. When it is not, wait for the user. When a hit is full, tell the user they already have it. - When nothing is found, say where you looked in one line, then continue with the playbook below.
Playbooks
Open the playbook that matches the next move.
| Next move | Playbook |
|---|---|
| Build or change code, a hook, a skill, a rule, a workflow, or config | playbooks/build.md |
| Log the ask in a tracker, or write a plan for it | playbooks/plan-or-log.md |
| Hand the ask to a worker, a thread, or another session | playbooks/delegate.md |
Layout
| File | What it holds |
|---|---|
SKILL.md |
The steps and the playbook index |
references/search-places.md |
Where to search, with the query to run in each place |
references/report-shape.md |
The four-point report and the "you already have it" answer |
playbooks/build.md |
The search and report before a build, and the pull request section |
playbooks/plan-or-log.md |
The search and report before a tracker entry or plan |
playbooks/delegate.md |
The search before a brief, and what the brief carries |
04 同仓库更多 Skills
update
Fast-forwards a local repository's main branch to a remote's main after confirming the repo path and source remote through AskUserQuestion. Use when the user says '/update', 'update main', 'fast-forward main', 'sync main from origin', 'pull latest main into <path>', or 'bring main up to date'.
source-command-sr-loop
Converging cleanup loop: repeat /simplify until clean, then repeat /code-review --fix until clean
skill-builder
Skill lifecycle: classify, scaffold, write via the skill-writer-agent, self-audit, compose sub-skills, polish description triggers, enforce deterministic scripts. Triggers: build a skill, new skill workflow, improve this skill, optimize skill description, skill development lifecycle, skill modularity, skill composition, description trigger catalog, deterministic skill scripts.
session-tidy
Audit, clean, and consolidate session logs in the Obsidian vault. Fixes format drift, resolves orphaned next-steps, updates stale statuses, and generates project rollup summaries. Use when session logs feel cluttered or before starting a new project milestone. Triggers on '/session-tidy', 'tidy sessions', 'clean up session logs', 'session audit'.
session-log
Logs a session report as an HTML page, tracks vault context, extracts decisions, and outputs a /rename command. Use for /session-log, 'journal this session', 'log this work', 'session report', 'summarize/log/record this session', 'save session', 'capture session', or 'document what we did'.
run-claude-dev-env
Build, install, run, and test the claude-dev-env installer. Use when asked to run claude-dev-env, install the Claude Code config into ~/.claude, drive the installer, smoke-test it against a sandbox, or run its test suite.