com um clique
yarstack
yarstack contém 11 skills coletadas de yarlson, com cobertura ocupacional por repositório e páginas de detalhe dentro do site.
Skills neste repositório
Use when a user needs architecture or product-design sparring on system design, runtime boundaries, config, deployment, operations, or implementation plans; ask one focused question at a time.
Use when ready to ship confirmed local changes through a draft PR: check dirty-worktree scope, create a branch, stage only intended paths, commit, push, open a PR, wait for CI, and fix red checks.
Use when creating or updating current-state project context documentation under docs/context/.
Use when reviewing local code changes before a PR: review my changes/code, check my work, security review, review before push; rank bugs, security, perf, and production risks.
Triage CodeRabbitAI review comments on current PR, fix legitimate issues, push, resolve threads
Create a committed Markdown todo in ~/.create-todo from a todo, task, follow-up, $create-todo request, or current conversation context.
Use when creating concise Markdown docs-as-code for critical user journeys, flows, acceptance scenarios, service blueprints, telemetry, portfolios, story maps, and coverage matrices.
Commit all changes, push, wait for CI, fix if red, iterate until green
Use when an agent writes or rewrites implementation plans, PLAN.md files, roadmap phases, sprint-sized technical plans, or execution plans under an extremely strict maintainability bar. Trigger when user wants plans that make later implementation avoid strict code-quality review traps: structural regressions, spaghetti branching, wrong-layer logic, file sprawl, bad abstractions, loose contracts, missing tests, stale docs, or vague phases.
Use when reviewing infra or IaC changes before plan, apply, or deploy: Terraform, deploy config, cloud config, network exposure, IAM/RBAC, destructive changes, secrets, and cost.
Use when an agent implements code and user wants extremely strict maintainability bar: avoid structural regressions, spaghetti branching, file-size sprawl, bad abstractions, type-boundary leaks, wrong-layer logic, duplicate helpers, brittle orchestration, any trap a strict code-quality review block. Trigger: "implement this so strict review finds nothing", "build brutally clean", "avoid review traps while coding", "ship code under a strict quality bar".