All authors
Claude Skills by yarlson
github.com/yarlson52 skills0 installs22 views
- Procedure PromotePromote 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.Votes: 0GitHub stars: 3
- Wiki CaptureConvert 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.Votes: 0GitHub stars: 3
- Wiki InitializeCreate 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.Votes: 0GitHub stars: 3
- Wiki MaintainAudit 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.Votes: 0GitHub stars: 3
- Wiki RecallRetrieve 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.Votes: 0GitHub stars: 3
- Wiki ReconcileSearch, 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.Votes: 0GitHub stars: 3
- Alternatives ExploreGenerate materially different approaches to a product, workflow, or system problem, compare them with the conventional approach, and recommend one bounded experiment. Use when the user explicitly asks for bold, contrarian, experimental, or non-incremental alternatives; not for the smallest design that meets stated requirements, which belongs to system-design.Votes: 0GitHub stars: 3
- Architecture RefineSettle open product or system architecture decisions with the user, one question at a time, before a plan or contract update. Use when a design has choices that only the user can make, such as tradeoffs in ownership, persistence, deployment, or migration; not for proposing a complete design, which belongs to system-design.Votes: 0GitHub stars: 3
- Behavior ImplementImplement one observable behavior or bug fix with red-green-refactor, writing a focused test that fails first, the minimum code that passes it, and then a behavior-preserving cleanup. Use for product behavior changes; for tooling or infrastructure, use it only when native checks such as linters, validators, dry runs, or plans cannot show the behavior.Votes: 0GitHub stars: 3
- Bug Report ReproduceReproduce a user, customer, or support-reported problem with synthetic data, prove the cause with a temporary test, record a narrated click-through walkthrough of the symptom, and report what was and was not proven. Use when the user links a bug report, support thread, or ticket and asks to reproduce it, find the cause, or show a recording or walkthrough video; not for read-only questions without a report, which belong to system-investigate, or for planned feature work.Votes: 0GitHub stars: 3
- Change Cleanup ReviewReview a complete change for unwanted scope, duplicate or leftover artifacts, churn or prose that hides the change, hollow verification, and work shifted to reviewers. Use before human review and again after review-driven fixes; not for correctness, security, design, or test-sufficiency review, and not to guess whether an AI wrote the change.Votes: 0GitHub stars: 3
- Changes ExplainExplain 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.Votes: 0GitHub stars: 3
- Changes ReportReport 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.Votes: 0GitHub stars: 3
- Ci ReviewAudit CI workflow design 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.Votes: 0GitHub stars: 3
- Claude ReviewRun 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.Votes: 0GitHub stars: 3
- Cli ControlVerify 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; not for browser, desktop, or Electron interfaces, which belong to ui-control.Votes: 0GitHub stars: 3
- Code ReviewOrchestrate an adaptive multi-agent review of a pull request or local change that builds a structural and semantic brief, assigns risk-based reviewer lanes at runtime, challenges and deduplicates their findings, verifies each one, and renders an evidence-backed review. Use when a pull request or local change needs independent review lanes, adversarial challenge, or GitHub-ready findings.Votes: 0GitHub stars: 3
- Coderabbit TriageTriage 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.Votes: 0GitHub stars: 3
- Crap Index AssessAssess method-level change risk with the Change Risk Anti-Patterns (CRAP) index and recommend focused testing or complexity reduction. Use when the user asks what CRAP means or how to calculate, interpret, or reduce a CRAP score, or when the repository's configured CRAP check covers changed methods; not as a general quality verdict or merge gate.Votes: 0GitHub stars: 3
- Critical Journey DocumentCreate 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; not for implemented-system context under docs/context/, which belongs to repo-context-document.Votes: 0GitHub stars: 3
- Dependency ReviewReview dependency necessity, identity, provenance, and reproducibility without modifying them. Use when manifests, lockfiles, vendor state, generated dependency state, registries, fetched tools, or version pins change.Votes: 0GitHub stars: 3
- Docs Drift ReviewReview documentation for drift caused by the current code or configuration change. Use to identify concrete inaccuracies and, when authorized, repair only directly affected documentation; not for general documentation quality, which belongs to docs-review.Votes: 0GitHub stars: 3
- Docs ReviewAudit or improve general repository documentation against implemented behavior. Use for deliberate README or documentation-quality work not owned by a more specific documentation skill.Votes: 0GitHub stars: 3
- Explainer Video CreateCreate a narrated 3Blue1Brown-style animated explainer video about how an existing project feature works, using manim with ElevenLabs or local text-to-speech. Use when the user asks for an explainer, walkthrough, or teaching video about code, architecture, or system behavior; not for promotional clips or slide decks.Votes: 0GitHub stars: 3
- Go Code ReduceFind 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.Votes: 0GitHub stars: 3
- Infra ReviewReview 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.Votes: 0GitHub stars: 3
- Jira Issue CreateCreate 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.Votes: 0GitHub stars: 3
- Jira Issue DeliverAutonomously 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.Votes: 0GitHub stars: 3
- Jira Issue RefineRefine 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.Votes: 0GitHub stars: 3
- Marketing Claims ReviewAudit 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.Votes: 0GitHub stars: 3
- Phase CommitCreate 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.Votes: 0GitHub stars: 3
- Phase ImplementImplement 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.Votes: 0GitHub stars: 3
- Phase ReviewReview one validated phase for behavior-preserving structural regressions introduced or materially worsened by the change. Use after phase validation and before final delivery.Votes: 0GitHub stars: 3
- Phase ValidateValidate 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.Votes: 0GitHub stars: 3
- Plan CreateCreate 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.Votes: 0GitHub stars: 3
- Plan DeliverAutonomously deliver an approved implementation plan to a ready GitHub pull request. Use when the user supplies a plan in the conversation or a file and authorizes implementation, commits, pushes, PR state changes, CI remediation, and resolution of requested automated review feedback; use jira-issue-deliver when the contract is a Jira issue.Votes: 0GitHub stars: 3
- Plan UpdateMake 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.Votes: 0GitHub stars: 3
- Pr DraftPublish 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.Votes: 0GitHub stars: 3
- Repo Context DocumentCreate, update, or consolidate adopted current-state documentation under docs/context/. Use for durable implemented architecture, ownership, runtime, domain, flow, terminology, or engineering-practice context.Votes: 0GitHub stars: 3
- Roadmap Task DeliverDeliver 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.Votes: 0GitHub stars: 3
- Rollout Readiness ReviewReview 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.Votes: 0GitHub stars: 3
- Security ReviewReview 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.Votes: 0GitHub stars: 3
- Skill OptimizeReduce the loaded token cost of one existing skill without weakening its trigger, decisions, safety, or outcome. Use when the user supplies a skill path and authorizes a focused rewrite, not to create or repurpose a skill.Votes: 0GitHub stars: 3
- Spec UpdateMake 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.Votes: 0GitHub stars: 3
- System DesignDesign 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.Votes: 0GitHub stars: 3
- System InvestigateInvestigate 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.Votes: 0GitHub stars: 3
- Tech Debt AuditAudit a whole repository or subsystem for technical debt with at most four non-overlapping read-only subagents, lead verification, and interest-over-principal ranking, and produce an evidence-backed debt register. Use when the user wants to find, size, or prioritize existing debt across a codebase; not for reviewing one change, which belongs to code-review.Votes: 0GitHub stars: 3
- Technical SpikeResolve 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.Votes: 0GitHub stars: 3
- Test DesignDesign or write reproducible tests matched to behavioral risk before implementation. Use for product behavior; for tooling or infrastructure, use it only when native checks such as linters, validators, dry runs, or plans cannot show the behavior.Votes: 0GitHub stars: 3
- Test Gap ReviewReview whether existing tests and verification credibly prove a scoped behavior contract. Use during validation when evidence may omit important behavior or provide false confidence.Votes: 0GitHub stars: 3