最近新增
刚加入收藏的新技能，抢先试用。
stack-decomposition-format
KingInYellows
Structured format contract for "## Stack Decomposition" sections in plan documents, shared by gt-stack-plan (producer) and flow:work (consumer). Use when writing or parsing a Stack Decomposition section.
smart-submit
KingInYellows
Stage, audit, commit, and submit uncommitted changes via Graphite, with parallel code-review agents. Use when user says "submit this", "ship it", or "commit and push", or has uncommitted work to turn into a PR. Requires uncommitted changes — a clean, already-committed branch needs only gt submit; amending an already-submitted branch is the gt-amend skill.
gt-sync
KingInYellows
Pull latest trunk, restack all tracked branches, and untrack branches whose PRs merged. Use when user says "sync with main", "rebase my stack", or "pull latest", after PRs merge, or when gt reports "needs restack". Not for deleting stale local-only branches — use the gt-cleanup skill.
gt-stack-plan
KingInYellows
Decompose a feature into stacked PRs, ordered by dependency (plan-only). Use when breaking a feature into reviewable stacked PRs.
gt-setup
KingInYellows
Validate Graphite CLI prerequisites and configure settings for AI agent workflows. Use when first installing the plugin, after Graphite auth changes, or when gt commands fail.
gt-nav
KingInYellows
Visualize your Graphite stack and navigate between its branches. Use when user says "show my stack", "where am I in the stack", "go up/down a branch", or "checkout the top of the stack". Not for restacking, syncing, or cleanup — use the gt-sync or gt-cleanup skill.
gt-merge
KingInYellows
Merge the current stack's pull requests, from trunk up to the current branch, via Graphite. Use when the user says "merge my stack" or "land these PRs" and the stack is fully reviewed and ready.
gt-cleanup
KingInYellows
Scan local branches for staleness and divergence, then delete or reconcile them with safeguards. Use when user says "clean up my branches" or "which branches are stale". For deleting branches whose PRs merged — and for pulling trunk or restacking — use the gt-sync skill.
gt-amend
KingInYellows
Fold working-tree changes into the current branch commit, audit them, and re-submit via Graphite. Use when user says "amend this", "add this to the current PR", "fold this fix in", or has follow-up edits for an already-submitted branch. Not for starting new work — use the smart-submit skill instead.
audit-review
KingInYellows
Run 1-3 parallel quick-audit passes (code quality, security, error handling) over a diff and gate on findings. Use when smart-submit or gt-amend need to audit uncommitted changes before committing.
debt-complexity-scan
KingInYellows
Scan complexity debt. Use when asked about risky control flow.
cursor-plan
KingInYellows
'Validate offline Cursor plans. Use when preparing Cursor tasks.'
cursor-delegation
KingInYellows
"Host-neutral reference for the Cursor Cloud Agent delegation lifecycle, the yellow-cursor CLI's JSON contract, and its safety/idempotency rules. Use when building or reasoning about a surface that delegates work to a Cursor Cloud Agent through the CLI."
worktree-inventory
KingInYellows
"List existing Git worktrees and their branch, detached, lock and prune status without changing the repository. Use when inspecting worktree locations or diagnosing isolation."
stack-provider-router
KingInYellows
'Resolve which stacked-PR provider is active and route provider-specific work to it, or refuse when the state is ambiguous. Use when a workflow needs to know whether Graphite or GitHub native stacks is in effect before running a stack operation.'
stack-provider-guard
KingInYellows
'Enforce the stacked-PR provider invariants before any provider-changing action — exactly one enabled, managed scopes fail closed, no direct settings edits, no silent fallback. Use when validating a proposed provider switch or auditing current provider state.'
session-history
KingInYellows
"Search prior sessions across Claude Code, Devin, and Codex for the same problem or topic. Use when the current session cannot see prior context — after agent compaction, session boundary, or when reconstructing a multi-session decision trail. This searches raw prior-session transcripts; for distilled learnings, use ruvector recall (/ruvector:memory)."
security-fencing
KingInYellows
"Canonical prompt-injection hardening block for agents that analyze untrusted content (source code, CI logs, workflow files). Use when authoring an agent that reads untrusted input — copy the appropriate variant verbatim into the agent body; only pure output-only agents (no file reading, no untrusted input) are exempt."
multi-host-fleet
KingInYellows
Multi-host plugin credential and config reference for yellow-plugins. Use when setting up a new workstation, configuring CI/devcontainer, replicating credentials across a fleet, or wiring a secrets manager. Documents the canonical shell env var names for every credential-bearing plugin.
morph-discovery-pattern
KingInYellows
"Morph discovery + fallback pattern — discover edit_file and warpgrep at runtime via ToolSearch, prefer them for large edits and intent-based search, silently fall back to Edit/Grep when yellow-morph is missing. Use when authoring agents that edit files or run semantic searches."
memory-remember-pattern
KingInYellows
"Tiered-Remember-After-Act pattern for ruvector — record learnings via hooks_remember at workflow completion with signal-strength tiers (Auto/Prompted/Skip). Use when authoring commands that should compound institutional memory from workflow outcomes."
memory-recall-pattern
KingInYellows
"Recall-Before-Act pattern for ruvector — query past learnings via hooks_recall at workflow start. Use when authoring commands or agents that should seed a workflow with relevant institutional memory before executing."
local-config
KingInYellows
"Defines the yellow-plugins.local.md per-project config file schema. Use when authoring commands that should accept per-project overrides for review pipeline behavior, reviewer set narrowing, depth controls, or focus-area filtering."
ideation
KingInYellows
"Generate 3 grounded approaches to a soft problem, then hand the chosen one off to brainstorm-orchestrator. Use when the problem statement is still vague or /flow:brainstorm narrows too quickly."