KingInYellows
Official@kinginyellows
Offers standardized architectural patterns and governance frameworks for multi-agent systems, repository maintenance, and technical documentation lifecycle management.
Agent Skills by KingInYellows
Showing 34 vetted skills indexed across 1 GitHub repositories.
KingInYellowsce-compound-refresh
Audit docs/solutions against the codebase and apply evidence-based updates.
KingInYellowsce-code-review
Orchestrate multiple reviewer personas to detect code issues and generate deduplicated reports.
KingInYellowsce-resolve-pr-feedback
Coordinate parallel agents to triage and resolve GitHub PR feedback threads.
KingInYellowsce-compound
Coordinate parallel subagents to document solved problems into Markdown artifacts.
KingInYellowsce-doc-review
Coordinate multi-agent document reviews to surface role-specific issues.
KingInYellowsce-agent-native-architecture
Orchestrate loop-based prompts with atomic tools for agent-native architectures.
KingInYellowsce-agent-native-audit
Audit agent-native architecture across eight principles and produce a scored report.
KingInYellowsce-worktree
Create isolated git worktrees for parallel feature development and PR reviews.
KingInYellowsce-debug
Diagnose bugs through a phase-based investigation from symptom to root cause.
KingInYellowsce-ideate
Generate grounded ideation with multi-frame critique from repository context.
KingInYellowsce-optimize
Orchestrate metric-driven iterative experiments with baselines, gates, and durable logs.
KingInYellowspr-review-workflow
Centralize PR review patterns and conventions for yellow-review commands and agents.
KingInYellowsci-conventions
Standardize CI failure analysis for self-hosted GitHub Actions runners.
KingInYellowsdiagnose-ci
Diagnose GitHub Actions CI failures on self-hosted runners using failure patterns F01-F12.
KingInYellowstest-conventions
Standardize config schemas, severity levels, and credential handling for yellow-browser-test.
KingInYellowsagent-browser-patterns
Document agent-browser usage patterns for refs, sessions, and safety rules.
KingInYellowsresearch-patterns
Enforce slug naming and markdown structure for research outputs.
KingInYellowsdebt-conventions
Define unified debt scoring frameworks and JSON output schemas for scanner agents.
KingInYellowschatprd-conventions
Document and enforce ChatPRD conventions for MCP interactions.
KingInYellowssemgrep-conventions
Standardize Semgrep integration conventions for API usage, token handling, and triage workflows.
KingInYellowsmemory-query
Query ruvector's vector memory store before acting with graceful degradation.
KingInYellowsruvector-conventions
Define MCP schema and naming conventions for ruvector vector memory workflows.
KingInYellowsagent-learning
Record and retrieve agent learnings with RRF-based ranking and quality gates.
KingInYellowsdocs-conventions
Enforce standardized documentation templates and Mermaid diagram conventions across repositories.
Frequently Asked Questions About KingInYellows
FAQPage SchemaWhat specific tasks are enabled by these architectural patterns?▼
These patterns enable systematic code review orchestration, GitHub PR feedback triage, documentation lifecycle management, and standardized CI failure diagnostics. They provide structured frameworks for multi-agent interaction, vector memory querying, and repository-wide configuration management to ensure consistency across complex development environments.
Which technical personas benefit from these conventions?▼
Platform engineers, technical leads, and repository maintainers benefit from these conventions. They are designed for teams managing multi-agent architectures, complex GitHub repository structures, and those requiring standardized protocols for code quality, documentation, and technical debt tracking.
What are the prerequisites for implementing these patterns?▼
Implementation requires a repository environment utilizing GitHub, standard Git version control, and support for MCP-compliant integrations. Users should have existing familiarity with YAML-based configuration, Semgrep for security analysis, and structured Markdown documentation practices to effectively adopt these standardized schemas and conventions.