Other skills

Use when a knowledge artifact needs review before sharing or execution. Not for source or remote-system changes.

The English summary is being prepared. Showing the original description.

Use when the user asks to classify a batch of projects against eligibility rules and generate an approval preview before creating hierarchical child documents.

The English summary is being prepared. Showing the original description.

Use when asked to summarize authored work over the last week or a named date range, commit range, or branch. Not for source or remote-system changes.

The English summary is being prepared. Showing the original description.

Use when a non-trivial change lands or is abandoned and its decision, rejected alternatives, and reason must be captured. Not for trivial or corrective changes: those belong in CHANGELOG.

The English summary is being prepared. Showing the original description.

Use when a user resumes work and needs an orientation card without full human recall. Not for packaging context for another agent or session: use handoff. Never source or remote-system changes.

The English summary is being prepared. Showing the original description.

Use when a measured cost surface needs one-change-at-a-time reduction under frozen guardrails. Not for speed-only optimization: use optimize.

The English summary is being prepared. Showing the original description.

Use when the user asks to view, export, or inspect a session transcript in a browser. Not for sharing a session: use session-share.

The English summary is being prepared. Showing the original description.

Use when the human returns after a gap, cannot follow the project, asks what happened, or wants a visual HTML recap page. Not for onboarding: use onboard. Not for handoff: use handoff.

The English summary is being prepared. Showing the original description.

Use when a human explicitly invokes a watcher cycle for an open pull request that must be watched until mergeable or blocked. Not for merge, force-push, or work outside the invoked cycle.

The English summary is being prepared. Showing the original description.

Use when a human explicitly asks to commit and push to the checked-out branch, including directly to the default branch, with no branch creation and no pull request. Not for a feature branch off the default: use commit-push-pr in its no-PR mode.

The English summary is being prepared. Showing the original description.

Use when a maintainer or collaborator explicitly asks to review and land one external pull request. Don't use for internal pull requests or landing without preserving contributor authorship.

The English summary is being prepared. Showing the original description.

Use when the user explicitly asks to choose which issues or pull requests to close interactively. Don't use for closing items without per-item selection and explicit approval.

The English summary is being prepared. Showing the original description.

Use when the user asks to find PRs to review or check the team review queue. Not for summarizing or resolving feedback on a specific PR: use resolve. Read-only.

The English summary is being prepared. Showing the original description.

Use when landing a queue of open PRs: gate each PR, sweep its review feedback to root cause, then merge, repair, hold, or close it. Human-only.

The English summary is being prepared. Showing the original description.

Use when the user wants to batch-close resolved or outdated tracker items. The agent never closes tracker items itself. Not for individual closure or items still under active work.

The English summary is being prepared. Showing the original description.

Use when a parser, protocol, or file format fuzzer stalls at fixed-token validation gates and needs a coverage dictionary. Not for patching the SUT: use fuzzing-obstacles.

The English summary is being prepared. Showing the original description.

Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.

The English summary is being prepared. Showing the original description.

Use when asked to commit and push a feature branch, with or without a pull request. Its no-PR mode publishes without a PR. Not for a PR body alone: use create-pull-request.

The English summary is being prepared. Showing the original description.

Use when the user wants to elicit refused directions, generalize them, and close matching tracker items as not planned. Not for duplicates, spam, or items closed as completed or obsolete.

The English summary is being prepared. Showing the original description.

Use when a user needs to measure fuzz corpus coverage, explain a coverage plateau, or turn uncovered regions into campaign work. Not for harness creation: use fuzz-harness-writing.

The English summary is being prepared. Showing the original description.

Use when asked to identify and bypass checksums, nondeterminism, or validation barriers that block fuzzing coverage. Not for dictionary creation: use fuzzing-dictionary. Local writes only.

The English summary is being prepared. Showing the original description.

Use when the user says "atomic PRs" or requests one issue or PR per logical change. Don't use for single-change pushes or uncommitted change-sets.

The English summary is being prepared. Showing the original description.

Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts. Not for people-mediation conflicts: use culture-conflict-mediation.

The English summary is being prepared. Showing the original description.

Use when the user asks to propose an issue, file or open a bug report, or turn a reported defect into a tracked issue. Not for fixing the defect, triaging existing issues, or reviewing PRs.

The English summary is being prepared. Showing the original description.