yarlson
- 48 skills
- 0 followers
- 3 repo stars
- 2 months ago last updated
- ▌ Plan Update · yarlsonMake the smallest evidence-backed correction to implementation-plan mechanics. Use when implementation or validation proves incorrect ordering, prerequisites, phase scope, dependencies, steps, or validation gates.
- ▌ Spec Update · yarlsonMake a minimal evidence-backed update to a non-plan product, architecture, API, schema, or behavior contract. Use when implementation or validation cannot determine correctness from the current authoritative contract.
- ▌ Test Design · yarlsonDesign or write reproducible tests matched to behavioral risk before implementation. Use for product behavior and for engineering tooling and infrastructure only when native checks are insufficient and concrete complexity or failure risk warrants proportionate dedicated tests.
- ▌ Wiki Capture · yarlsonConvert a completed session or queued Yarbrain session locator into an immutable episode and reviewable knowledge or procedure candidates. Use after substantial work, before context loss, or when pending session records need extraction; never update canonical notes or active skills.
- ▌ Infra Review · yarlsonReview infrastructure-as-code and rendered deployment configuration without modifying it. Use before plan, apply, or deploy when targeting, replacement, state, availability, cost, ordering, or recovery blast radius may change.
- ▌ Phase Commit · yarlsonCreate one local commit for a completed, validated, and reviewed unit of work. Use only when the user explicitly requests a commit without pushing or other delivery actions.
- ▌ Phase Review · yarlsonReview one validated phase for behavior-preserving structural regressions introduced or materially worsened by the change. Use after phase validation and before final delivery.
- ▌ Text Improve · yarlsonEdit or rewrite human-readable technical prose for clarity while preserving meaning and precision. Use for comments, docstrings, documentation, commit or pull request text, issues, reports, runbooks, logs, errors, command help, and similar writing rather than factual, structural, or marketing review.
- ▌ Wiki Maintain · yarlsonAudit and conservatively maintain a configured Yarbrain vault for structural errors, stale knowledge, duplication, conflicts, unprocessed evidence, and skill drift. Use periodically or when recall quality declines; make deterministic checks first and require approval for semantic consolidation or archival.
- ▌ Claude Review · yarlsonRun an independent Claude Opus review of the complete current change against the repository's default branch, then verify its findings locally. Use after focused checks pass when you want a second model to review the change before further edits or delivery.
- ▌ System Design · yarlsonDesign the smallest system or feature architecture that satisfies stated current requirements, for a greenfield product or a new capability in an existing codebase. Use when the user wants a proposed design with components, non-goals, and growth triggers; not for investigating existing behavior, settling one open decision, or planning phases.
- ▌ Wiki Reconcile · yarlsonSearch, compare, and reconcile pending Yarbrain memory candidates with canonical semantic notes through reviewable patches. Use when processing inbox/memory candidates, resolving conflicting evidence, or applying an explicitly approved knowledge patch; do not capture sessions or promote procedures.
- ▌ Changes Report · yarlsonReport all repository changes that entered a target branch during one required date or period, grouped by product change and written as plain English for a broad audience. Use for daily, weekly, date-range, or relative-period change summaries rather than explaining one known diff.
- ▌ Go Code Reduce · yarlsonFind and, when authorized, apply maintainable Go code reductions. Use when a user asks to reduce Go lines, boilerplate, duplication, or obsolete idioms without changing behavior; not for general implementation or style review.
- ▌ Phase Validate · yarlsonValidate exactly one implemented phase or scoped change against its authoritative contract. Use after implementation to re-derive criterion-level conclusions from current evidence and fix only required implementation gaps.
- ▌ Wiki Initialize · yarlsonCreate or adopt a user-controlled Yarbrain Markdown vault and configure lifecycle hooks to find it. Use when setting up Yarbrain, moving its vault, or repairing a missing vault structure; do not use for routine capture or maintenance.
- ▌ Changes Explain · yarlsonExplain a pull request, commit range, branch, or local diff from a system-design perspective. Use for practical understanding of changed behavior, boundaries, flow, ownership, operations, risks, and verification rather than defect review.
- ▌ Phase Implement · yarlsonImplement exactly one selected phase from an authoritative repository plan. Use when a named phase or equivalent scoped implementation unit must be completed without later-phase work.
- ▌ Security Review · yarlsonReview a focused trust-boundary or exploit-path change without modifying it. Use when work introduces or materially changes untrusted input, privilege decisions, secret flow, dangerous sinks, or agent and tool capabilities.
- ▌ Technical Spike · yarlsonResolve one correctness-blocking external or version-specific technical uncertainty through bounded investigation. Use when cheap local inspection cannot establish framework, library, tool, runtime, protocol, or platform behavior needed by the current task.
- ▌ Test Gap Review · yarlsonReview whether existing tests and verification credibly prove a scoped behavior contract. Use during validation when evidence may omit important behavior or provide false confidence.
- ▌ Procedure Promote · yarlsonPromote a repeated, verified Yarbrain procedure candidate into a user-owned Agent Skill or propose an update to an existing one. Use after the same procedure succeeds in independent episodes or when the user explicitly requests reusable automation; do not promote facts, policy, or unexplained workarounds.
- ▌ Coderabbit Triage · yarlsonTriage unresolved CodeRabbit feedback on the current GitHub pull request. Use for read-only disposition and, only when separately authorized, scoped remediation and remote thread closure.
- ▌ Crap Index Assess · yarlsonAssess method-level change risk with the Change Risk Anti-Patterns (CRAP) index and recommend focused testing or complexity reduction. Use when a repository configures CRAP measurement, cyclomatic complexity and automated test coverage data are available, or a user asks what CRAP means, how to calculate or interpret it, or how to reduce a CRAP score.
- ▌ Dependency Review · yarlsonReview dependency provenance and reproducibility without modifying them. Use when manifests, lockfiles, vendor state, generated dependency state, registries, fetched tools, or version pins change.
- ▌ Docs Drift Review · yarlsonReview documentation for drift caused by the current code or configuration change. Use to identify concrete inaccuracies and, when authorized, repair only directly affected documentation.
- ▌ Jira Issue Create · yarlson bundleCreate one or more Jira issues through acli from user-approved drafts using heading-based Context, Acceptance criteria, and Engineering notes sections. Use only when explicitly invoked to create Jira issues; use jira-issue-refine when requirements still need refinement.
- ▌ Jira Issue Refine · yarlsonRefine one draft or existing Jira issue into a clear, evidence-backed, bounded delivery contract without implementing it. Use when creating or revising an issue before engineering handoff, especially when behavior, repository ownership, acceptance evidence, dependencies, risk, environment needs, or scope remain unclear.
- ▌ Behavior Implement · yarlsonImplement behavior through a red-green-refactor cycle when focused automated tests are proportionate. Use for product behavior changes and for engineering tooling and infrastructure only when native checks are insufficient and concrete complexity or failure risk warrants dedicated tests.
- ▌ Jira Issue Deliver · yarlsonAutonomously deliver one Jira issue from intake to a ready GitHub pull request. Use only when the user authorizes implementation, commits, pushes, PR state changes, CI remediation, and resolution of requested automated review feedback.
- ▌ System Investigate · yarlsonInvestigate an underdefined product, codebase, architecture, integration, or operational question through read-only repository tracing, bounded runtime evidence, and current public research. Use when the user wants to validate suspected behavior, explain why it occurs, compare plausible designs for existing behavior, or recommend the smallest safe change before planning or implementation; not for designing a new system or feature, which belongs to system-design.
- ▌ Architecture Refine · yarlsonRefine underdefined product or system architecture through focused interactive decisions. Use when the user wants architecture sparring before a formal implementation plan or contract update.
- ▌ Alternatives Explore · yarlsonGenerate and evaluate genuinely different approaches to a product, workflow, or system problem. Use when the user explicitly wants a bold, contrarian, experimental, or non-incremental alternative and a testable recommendation.
- ▌ Roadmap Task Deliver · yarlsonDeliver the first eligible unfinished roadmap task through implementation, review, green CI, PR merge, and a task-status update. Use for autonomous delivery from local roadmap and task files. Files can be outside the code repository or outside Git.
- ▌ Change Cleanup Review · yarlsonReview a complete change for unwanted scope, redundant or residual artifacts, review-obscuring churn or prose, hollow verification, and work shifted to reviewers. Use before human review and after review-driven fixes, not for general implementation review or AI-authorship inference.
- ▌ Repo Context Document · yarlsonCreate, update, or consolidate adopted current-state documentation under docs/context/. Use for durable implemented architecture, ownership, runtime, domain, flow, terminology, or engineering-practice context.
- ▌ Marketing Claims Review · yarlsonAudit or, when authorized, rewrite persuasive product claims against shipped-product evidence. Use for landing pages, marketing-heavy READMEs, feature or pricing pages, comparisons, and calls to action.
- ▌ Rollout Readiness Review · yarlsonReview cross-cutting operational readiness after implementation and before deployment. Use when a concrete change may alter runtime prerequisites, failure visibility, deployment order, rollback, recovery, or production failure modes.
- ▌ Critical Journey Document · yarlsonCreate one concise evidence-linked product journey record for one actor pursuing one goal. Use when product behavior needs traceable ownership, acceptance, telemetry, or service-flow documentation for a current decision or delivery gate.
- ▌ Pr Draft · yarlsonPublish confirmed local changes as a monitored GitHub draft pull request. Use only when the user authorizes branch creation, scoped staging, commit, push, draft PR creation, and CI follow-up.
- ▌ CI Review · yarlsonAudit CI workflow architecture and effectiveness without modifying it. Use when triggers, jobs, commands, quality gates, caches, artifacts, matrices, permissions, release paths, or deployment automation may be stale, redundant, unsafe, or unjustified.
- ▌ UI Control · yarlsonVerify graphical browser, desktop, or Electron behavior through the actual interface. Use when screenshot, accessibility, console, network, trace, or browser-driven evidence is required; exclude terminal-hosted interfaces.
- ▌ Wiki Recall · yarlsonRetrieve a small, relevant set of current Yarbrain notes, episodes, and approved procedures for an upcoming task. Use before substantial debugging, design, planning, or repeated work where prior knowledge can change the approach; remain read-only.
- ▌ CLI Control · yarlsonVerify terminal-hosted CLI or TUI behavior with repeatable local evidence. Use for output, prompts, interactive input, signals, hangs, resizing, startup, exit status, or terminal restoration.
- ▌ Code Review · yarlsonOrchestrate an adaptive multi-agent pull-request review that combines structural and semantic context, assigns risk-based reviewer prompts at runtime, deduplicates and verifies findings, and renders an evidence-backed review. Use when a pull request or local change needs independent review lanes, adversarial challenge, or GitHub-ready findings.
- ▌ Docs Review · yarlsonAudit or improve general repository documentation against implemented behavior. Use for deliberate README or documentation-quality work not owned by a more specific documentation skill.
- ▌ Plan Create · yarlsonCreate a final implementation-ready plan from a user brief, settled decisions, and repository evidence. Use when work needs ordered phases, concrete deliverables, dependencies, risks, and validation before coding.
- ▌ Roadmap Builder · yarlsonInteractive roadmap creation through structured questioning, optimized for ephemeral execution