其他技能

当用户的团队执行力出了问题——OKR完不成、计划总变、团队被动等指令——时激活此skill。 典型触发信号：目标定好了但执行走样、计划赶不上变化、团队只做被分配的事不主动思考。 不调用场景：执行良好只需微调、问题在战略层面而非执行层面、单人工作不需要团队执行力框架。 与"战略-战术辩证法"skill的区别：本skill解决"执行力的三个维度如何平衡"（执行层），后者解决"攻守层级的辩证设计"（策略层）。

中文简介正在准备中。当前显示原文说明。

Automatically fix skill problems (safe preview first). Also use with --prune to find and remove broken symlinks, empty directories, and orphaned skills. Trigger with '/janitor-fix'.

中文简介正在准备中。当前显示原文说明。

Use before proposing error definitions (propose_error_definitions) - how to read an error group, pick its category and action, write a match that catches one kind of error and nothing else, and when a definition should not be proposed at all

中文简介正在准备中。当前显示原文说明。

Use after the first trace of a diff and before the verdict - pick the attack-class skills each touched surface needs, give every risky surface a disposition, ask the coverage-critic questions (parallel paths, lifecycle modes, handoffs, second-order use), search variants of every HIGH/CRITICAL root cause, and run the literal obvious-things sweep

中文简介正在准备中。当前显示原文说明。

Use when the diff builds a filesystem path from input, extracts an archive, accepts an upload, serves a file or writes a temp file - traversal, symlinks, zip-slip, upload type and served content-type

中文简介正在准备中。当前显示原文说明。

Use when the diff adds or changes an endpoint, resolver, RPC, job or query that takes an object id, a role check, a request binding or a tenant filter - BOLA/IDOR, function-level authorization, mass assignment and tenant scoping

中文简介正在准备中。当前显示原文说明。

Use when training, tuning, comparing or evaluating a model — choosing the cross-validation scheme, baselines, tuning inside CV, thresholds and calibration, per-slice metrics, feature importance and error analysis

中文简介正在准备中。当前显示原文说明。

Use when you write or revise the analiz deliverable - the ONE self-contained HTML report (spec and plan as sections) a human reviews passage by passage

中文简介正在准备中。当前显示原文说明。

Use when updating the stakeholder - report in outcome language (what changed for users, what's next, what decision is needed), translate technical detail, and surface risks early

中文简介正在准备中。当前显示原文说明。

Use when a batch (desktop or mobile) release reaches awaiting_verdict or was rolled back - read-only checks that the published artifact really exists and is served, and the exact yank step for a bad tag

中文简介正在准备中。当前显示原文说明。

Use when any case fails or you reject a criterion - what goes in the review_criterion note, the failed case and the numbered need_revision comment, with severity

中文简介正在准备中。当前显示原文说明。

Use when you are about to hand off any change to a screen or component on a mobile repository - the size, text-scale and dark-mode matrix, the exact tool calls to see your own build, and the checklist that decides whether the screen is done.

中文简介正在准备中。当前显示原文说明。

Use after the targeted cases pass - choosing the adjacent behaviour this change can break from the PR's files and the component's links, and the per-repository smoke set

中文简介正在准备中。当前显示原文说明。

Use when organizing the workspace - create/rename initiative projects and link repositories to them directly, since these are factual actions needing no analiz or approval

中文简介正在准备中。当前显示原文说明。

Use when adding a screen, a tab, a deep link, or back-navigation handling - the per-stack navigation APIs, state preservation, auth-boundary resets, and how to verify a deep link actually opens the right screen.

中文简介正在准备中。当前显示原文说明。

Use when adding routes or deciding where state lives - carry resource ids and navigation-surviving state in the URL, keep route components thin, and lift shared state to a hook not a global store

中文简介正在准备中。当前显示原文说明。

Evidence rules for completion claims. Use before ticking an acceptance criterion, ending an implementation run, or writing anything that says something works, passes or is fixed.

中文简介正在准备中。当前显示原文说明。

Use when adding a use case, port, repository or adapter in a Go service — where each piece goes, how errors and transactions cross layers, and how to check the import direction

中文简介正在准备中。当前显示原文说明。

How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.

中文简介正在准备中。当前显示原文说明。

Template skill. Replace this with a specific description of when and why to use it.

中文简介正在准备中。当前显示原文说明。

Run a structured weekly review covering projects, habits, goals, and planning. Use when asked for a weekly review, week summary, or weekly planning session.

中文简介正在准备中。当前显示原文说明。

Manage persistent memory across sessions. Use when asked to remember, recall, forget, or review what was stored. Covers long-term facts (MEMORY.md), daily session logs, search, and memory housekeeping.

中文简介正在准备中。当前显示原文说明。

Use when inspecting or operating Herdr sessions, workspaces, tabs, panes, agents, terminal output, agent messaging, or waits.

中文简介正在准备中。当前显示原文说明。

Use when installing, updating, configuring, or troubleshooting Herdr, including missing commands, PATH errors, version differences, or Pi integration setup.

中文简介正在准备中。当前显示原文说明。