kinginyellows
- 80 skills
- 0 followers
- 3 hours ago last updated
- ▌ Ce Optimize · kinginyellows bundleRun metric-driven iterative optimization loops. Define a measurable goal, build measurement scaffolding, then run parallel experiments that try many approaches, measure each against hard gates and/or LLM-as-judge quality scores, keep improvements, and converge toward the best solution. Use when optimizing clustering quality, search relevance, build performance, prompt quality, or any measurable outcome that benefits from systematic experimentation. Inspired by Karpathy's autoresearch, generalized for multi-file code changes and non-ML domains.
- ▌ Ce Worktree · kinginyellows bundleCreate an isolated git worktree for parallel feature work or PR review. Use when starting work that should not disturb the current checkout, or when `ce-work` or `ce-code-review` offers a worktree option.
- ▌ Ce Agent Native Architecture · kinginyellows bundleBuild applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.
- ▌ Memory Recall Pattern · kinginyellowsRecall-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.
- ▌ Stack Provider Router · kinginyellowsResolve 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.
- ▌ Research Patterns · kinginyellowsReference conventions for how yellow-research derives slugs, formats reports, and saves output under docs/research/. Use when authoring or modifying yellow-research commands or agents that write research output.
- ▌ Github Stack Amend · kinginyellowsFold working-tree changes into the current branch commit and re-submit via gh stack. Use when user says "amend this" or "add this to the current PR" on the github stacked-PR provider.
- ▌ Github Stack Merge · kinginyellowsMerge a stacked PR via gh stack merge. Use when the user says "merge my stack" or "land this PR" on the github stacked-PR provider and the target is fully reviewed and ready.
- ▌ Github Stack Setup · kinginyellowsCheck 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.
- ▌ Semgrep Conventions · kinginyellows bundleShared conventions for Semgrep integration — triage state mappings, API patterns, fix strategy decision tree, rate limits, and security rules. Use when commands or agents need Semgrep-specific validation, error handling, or API reference.
- ▌ Github Stack Status · kinginyellowsReport 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.
- ▌ Github Stack Submit · kinginyellowsStage, commit, and submit uncommitted changes as a GitHub-native stacked PR. Use when user says "submit this" or "ship it" on the github stacked-PR provider and has uncommitted work to turn into a PR.
- ▌ Memory Remember Pattern · kinginyellowsTiered-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.
- ▌ Morph Discovery Pattern · kinginyellowsMorph 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.
- ▌ Github Stack Cleanup · kinginyellowsRemove 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.
- ▌ Test Conventions · kinginyellowsTesting conventions and configuration reference. Use when agents or commands need config schema, severity classification, report templates, or credential rules for browser testing.
- ▌ MCP Integration Patterns · kinginyellowsShared 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.
- ▌ Ruvector Conventions · kinginyellowsruvector workflow patterns and conventions reference. Use when commands or agents need ruvector context, MCP tool naming, current tool schemas, or error handling patterns.
- ▌ Agent Native Architecture · kinginyellowsReference for agent-native architecture principles: action parity, context parity, shared workspace, primitives over workflows, and dynamic context injection. Use when authoring agent integrations or designing tool surfaces.
- ▌ Test Skill · kinginyellowsSkill fixture used to validate the skill-reference resolver in lint-plugins.sh.
- ▌ Stack Decomposition Format · kinginyellowsStructured 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.
- ▌ Yellow Thermonuclear Review · kinginyellowsOpt-in structural maintainability rubric adapted from Cursor's thermo-nuclear code-quality review. Use only when explicitly asked for a thermonuclear review, a code-judo simplification pass, spaghetti-growth analysis, giant-file review, or an unusually strict architecture-quality audit; never apply it automatically to an ordinary review.
- ▌ Agent Browser Patterns · kinginyellowsagent-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.
- ▌ Ce Debug · kinginyellows bundleSystematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.
- ▌ Ce Ideate · kinginyellows bundleGenerate and critically evaluate grounded ideas about a topic. Use when asking what to improve, requesting idea generation, exploring surprising directions, or wanting the AI to proactively suggest strong options before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on X', 'surprise me', 'what would you change', or any request for AI-generated suggestions rather than refining the user's own idea.
- ▌
- ▌ Ce Doc Review · kinginyellows bundleReview requirements or plan documents using parallel persona agents that surface role-specific issues. Use when a requirements document or plan document exists and the user wants to improve it.
- ▌ Ce Code Review · kinginyellowsStructured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. Use when reviewing code changes before creating a PR.
- ▌ Ce Compound Refresh · kinginyellows bundleRefresh stale learning docs and pattern docs under docs/solutions/ by reviewing them against the current codebase, then updating, consolidating, replacing, or deleting the drifted ones. Trigger this skill when the user asks to refresh, audit, sweep, clean up, or consolidate stale docs in docs/solutions/ (phrases like "refresh my learnings", "audit docs/solutions/", "clean up stale learnings", "consolidate overlapping docs", "compound refresh", "/ce-compound-refresh"), or when ce-compound has just captured a new learning and flagged a specific older doc in docs/solutions/ as now inaccurate or superseded — invoke with the narrow scope hint ce-compound provides. Also trigger when the user points at a specific learning or pattern doc under docs/solutions/ and calls it stale, outdated, overlapping, or drifted. Do not trigger for general refactor, migration, debugging, or code-review work unless the user has explicitly directed attention to docs/solutions/ itself.
- ▌ Ce Resolve Pr Feedback · kinginyellowsResolve PR review feedback by evaluating validity and fixing issues in parallel. Use when addressing PR review comments, resolving review threads, or fixing code review feedback.
- ▌ Gt Nav · kinginyellowsVisualize 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.
- ▌ CI Setup · kinginyellowsCheck 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.
- ▌ Gt Sync · kinginyellowsPull 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.
- ▌ CI Status · kinginyellowsShow 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.
- ▌ Gt Amend · kinginyellowsFold 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.
- ▌ Gt Merge · kinginyellowsMerge 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 Setup · kinginyellowsValidate 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.
- ▌ Ideation · kinginyellowsGenerate 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.
- ▌ Optimize · kinginyellows bundleRun a metric-driven optimization pass: parallel candidate variants scored against an LLM-as-judge analytic rubric. Use when comparing approaches against a measurable goal — anywhere 'better' can be expressed as a per-criterion rubric. For session-level plan-adherence and scope-drift review, use /flow:review instead.
- ▌ CI Diagnose · kinginyellowsDiagnose a CI failure now — fetch the failed run, redact and match its logs against the F01-F12 pattern library, and report root cause with fixes. Use when a GitHub Actions run has failed and you want its root cause and a fix now (for the reference workflow guide, use the diagnose-ci skill).
- ▌ Diagnose CI · kinginyellowsReference 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.
- ▌ Debugging · kinginyellowsFind root causes systematically before fixing — trace the causal chain and form hypotheses with predictions for uncertain links. Use when debugging errors, test failures, stack traces, or when stuck after failed fix attempts. For delegating a stuck investigation to an independent Codex session, use /codex:rescue.
- ▌ Gt Cleanup · kinginyellows bundleScan 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.
- ▌ Plan Status · kinginyellowsShow a per-file checkbox progress dashboard of plans/ (open) and plans/complete/ (archived) plan documents. Use when reviewing which plans are ready to archive or checking work-in-flight at a glance.
- ▌ Audit Review · kinginyellowsRun 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.
- ▌ Smart Submit · kinginyellowsStage, 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.
- ▌ CI Conventions · kinginyellowsShared CI conventions reference (not an executable action) — validation rules, failure patterns (F01-F12), error catalog, and security patterns. Consult when agents or commands need CI-specific validation or pattern-matching reference.
- ▌ Git Worktree · kinginyellows bundleGit worktree management for isolated parallel development. Use when reviewing PRs in isolation, working on multiple features simultaneously, or when workflows offer worktree option.
- ▌ Local Config · kinginyellowsDefines 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.
- ▌ Gt Stack Plan · kinginyellowsDecompose a feature into stacked PRs, ordered by dependency (plan-only). Use when breaking a feature into reviewable stacked PRs.
- ▌ Brainstorming · kinginyellowsReference guide for iterative brainstorm dialogues — question techniques, YAGNI, approach exploration, and research escalation. Use when running /flow:brainstorm or authoring brainstorm-style agents.
- ▌ CI Runner Health · kinginyellowsCheck self-hosted runner health via SSH, with deep runner diagnostics folded in. Use when the user asks for runner status, whether a runner is healthy, or wants to verify infrastructure before diagnosing CI failures.
- ▌ CI Lint Workflows · kinginyellowsLint 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.
- ▌ Codex Patterns · kinginyellowsCanonical conventions for shelling out to the OpenAI Codex CLI. Use when authoring or modifying commands or agents that invoke codex exec — choosing flags, sandbox and approval modes, and parsing its output.
- ▌ Session Handoff · kinginyellowsWrite a session-handoff artifact at plans/handoff/<YYYY-MM-DD>-<slug>.md capturing current task, workflow status, active artifact, open decisions, in-flight changes, and next action so a fresh session can resume without re-deriving context. Use when the user says "create a handoff", "save session state", "handoff before compact", "pick up where we left off next time", or a session is approaching a context/compaction boundary mid-task. Not the shell halt pattern — /flow:pick-next-shell halts by design after writing its expansion artifact and needs no handoff; use this for free-form session state only.
- ▌ Session History · kinginyellowsSearch 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).
- ▌ Stack Plan Style · kinginyellowsDisplay 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.
- ▌ MCP Health Probe · kinginyellowsCanonical 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'.
- ▌ Multi Host Fleet · kinginyellowsMulti-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.
- ▌ Security Fencing · kinginyellowsCanonical 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.
- ▌ Debt Conventions · kinginyellowsTechnical debt scoring framework and scanner patterns. Use when scanner agents need scoring rubrics, category definitions, safety rules, or output schemas.
- ▌ Devin Workflows · kinginyellows bundleDevin V3 API workflow patterns and conventions. Use when commands or agents need Devin API context, session management, or error handling.
- ▌ Docs Conventions · kinginyellowsShared documentation conventions — templates, diagram type selection, staleness detection, severity classification. Use when agents need doc generation or audit context.
- ▌ Memory Query · kinginyellowsStandard pattern for querying ruvector institutional memory before acting. Use when authoring new agents or commands that should query past patterns, findings, or solutions before executing.
- ▌ Stack Traversal · kinginyellowsInternal reference for the bottom-up Graphite stack-traversal procedure shared by /review:all and /review:resolve-stack. Use when a yellow-review command needs to walk a Graphite stack PR by PR in dependency order.
- ▌ Agent Native Audit · kinginyellowsAudit 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.
- ▌ Compound Lifecycle · kinginyellows bundleAudit, refresh, and consolidate `docs/solutions/` to keep the institutional knowledge catalog from rotting. Use when a `docs/solutions/` sweep is needed or after `knowledge-compounder` flags an older entry as superseded.
- ▌ Linear Workflows · kinginyellowsLinear workflow patterns and conventions reference. Use when commands or agents need Linear workflow context, issue writing guidance, or branch naming conventions.
- ▌ Agent Learning · kinginyellowsAgent learning patterns and quality guidelines. Use when commands or agents need to determine when and how to record learnings, apply quality gates, or retrieve past knowledge using ranked retrieval.
- ▌ Create Agent Skills · kinginyellows bundleExpert guidance for creating Claude Code skills and agents. Use when working with SKILL.md files, authoring new skills, creating slash commands, or designing agent workflows.
- ▌ Council Patterns · kinginyellows bundleCanonical reference for yellow-council reviewer contracts, CLI invocation, redaction, and output-parsing conventions. Use when authoring or modifying claude-reviewer, gemini-reviewer, opencode-reviewer, or the /council command.
- ▌ Cursor Delegation · kinginyellowsHost-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.
- ▌ Library Context · kinginyellows bundleUse when an agent needs official library docs, API examples, or migration guides. Canonical fallback chain: context7 → EXA → WebSearch. Preloaded by within-plugin agents; inlined verbatim by cross-plugin consumers.
- ▌ Github Stack Nav · kinginyellowsCheck out a stack target — stack number, PR number, PR URL, or branch. Use when user says "go to PR 42" or "show my stack and let me pick" on the github stacked-PR provider.
- ▌ Stack Provider Guard · kinginyellowsEnforce 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.
- ▌ Pr Review Workflow · kinginyellows bundleInternal reference for PR review workflow patterns. Use when agents or commands need shared conventions for adaptive selection, output format, or error handling.
- ▌ Github Stack Plan · kinginyellowsReport the current GitHub-native stack structure (read-only). Use when checking what branches/PRs are in the stack before submitting or merging.
- ▌ Github Stack Sync · kinginyellowsSync 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.
- ▌ CI Setup Runner Targets · kinginyellowsConfigure runner pool targets, routing rules, and semantic metadata for CI workflow optimization (wizard, YAML import, or GitHub API discovery). Use when setting up runner-aware CI optimization or after changing your runner fleet.
- ▌ Composio Patterns · kinginyellowsCanonical conventions for running batch workflows through the Composio MCP server. Use when authoring or modifying commands or agents that call Composio tools — the Workbench sandbox, Multi-Execute batching, and the local usage counter.