KingInYellows
@KingInYellows Organization
Public Skills
github-stack-setup
by KingInYellows
'Check GitHub-native stacked-PR prerequisites — gh CLI, authentication, and the official github/gh-stack extension. Use when first installing the plugin, after gh auth changes, or when /stack:status reports PARTIAL_TOOLING for the github provider.'
diagnose-ci
by KingInYellows
'Reference guide (not an executable action) for CI debugging workflows and the F01-F12 failure-pattern catalog on self-hosted runners. Consult when you need to understand debugging workflows or failure patterns; to actually run a diagnosis, use the ci-diagnose skill instead.'
agent-browser-patterns
by KingInYellows
"agent-browser usage patterns and conventions reference. Use when agents or commands need agent-browser context, ref-based workflow, session persistence, semantic locator fallbacks, or error handling patterns."
gt-nav
by 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.'
github-stack-sync
by KingInYellows
'Sync the local stack with trunk via gh stack sync, optionally pruning merged branches. Use when user says "sync with main" or "pull latest" on the github stacked-PR provider.'
github-stack-cleanup
by KingInYellows
'Remove local stack tracking, and by default also remote-unstack every PR via the GitHub API. Use when user says "clean up my stack" or "untrack this stack" on the github stacked-PR provider.'
ci-lint-workflows
by KingInYellows
'Lint GitHub Actions workflows for self-hosted runner issues (W01-W14). Use when checking workflows before pushing or finding common CI pitfalls; previews and confirms before applying any fix.'
gt-sync
by 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.'
morph-discovery-pattern
by 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."
stack-provider-guard
by 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.'
mcp-health-probe
by KingInYellows
"Canonical MCP server health classification (OFFLINE / DEGRADED / HEALTHY plus PRESENT (untested) refinement) for /<plugin>:status commands. Use when authoring a status command that needs to distinguish 'MCP never started' from 'MCP running but upstream API degraded'."
mcp-integration-patterns
by KingInYellows
"Shared patterns for ruvector recall/remember and morph discovery integration (the ruvector protocol constants are a replica of yellow-ruvector's canonical memory-query skill). Use when authoring commands or agents that should leverage institutional memory and advanced editing tools."
memory-remember-pattern
by 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."
agent-native-audit
by KingInYellows
"Audit checklist for evaluating an existing codebase against agent-native architecture principles to identify parity gaps. Use when auditing for agent-native readiness, before adding a new agent capability, or when triaging agent-behavior regressions."
gt-merge
by 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.'
github-stack-plan
by KingInYellows
'Report the current GitHub-native stack structure (read-only). Use when checking what branches/PRs are in the stack before submitting or merging.'
ci-setup
by KingInYellows
'Check CI prerequisites and configure the self-hosted runner SSH config. Use when first installing the plugin, after adding runners, or when CI commands fail with auth or connectivity errors.'
cursor-delegation
by 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."
memory-recall-pattern
by 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."
test-conventions
by KingInYellows
"Testing conventions and configuration reference. Use when agents or commands need config schema, severity classification, report templates, or credential rules for browser testing."
stack-decomposition-format
by 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.'
ci-status
by KingInYellows
'Show recent CI workflow run status. Use when the user asks for CI status, recent builds, what is running, or needs to find a run ID for diagnosis.'
stack-plan-style
by KingInYellows
'Display guidance for presenting a stacked-PR plan — ordered branch tree with intent, commit type, and dependency notes. Use when gt-stack-plan presents a stack plan for user confirmation.'
github-stack-status
by KingInYellows
'Report GitHub-native stacked-PR tooling readiness and point to /stack:status (yellow-core) for the authoritative active-provider answer. Use when checking why gh stack tooling is unavailable or which stacked-PR provider is currently active.'