Menu
SkillsMP has collected 19 skills from Railly/skills. Open a skill to review its source and details.
Showing 19 of 19 collected skills.
Assess one already-selected GitHub issue, pull request, or manual request before any factory workflow is admitted. Classify the real intent, preserve evidence and uncertainty, recommend the minimum workflow, and stop for human confirmation. Use when a source…
Reduce code size, PR additions, duplication, ceremony, or maintenance surface while preserving behavior and regression protection. Use whenever the user asks to simplify, deduplicate, delete unnecessary code or tests, reduce LOC, shrink a diff below a line…
Test whether behavioral coverage can reject realistic wrong implementations. Use when tests are green but may be weak, after fixing a bug, and whenever code implements or changes a protocol, parser, serializer, state machine, lifecycle, event translation,…
Gate a diff before pushing or requesting review: deterministic checks first, then focused lenses selected by what the diff changes. Use before opening or updating a PR, when asked to pre-review a change, or after an external review round to harvest each…
Survey an unfamiliar or shared issue backlog, qualify a small set of worthwhile contributor-side candidates, compare them in an evidence-backed matrix, recommend one, let the user make the final selection, and seed the canonical Issue Contract. Use for…
Pressure a system's failure paths. Use to audit or verify timeouts, cancellation, cleanup, retries, idempotency, partial writes, recovery, leaks, bounded queues or caches, overload, backpressure, dependency failure, malformed upstream data, cross-platform…
Snapshot the reference graph of a GitHub PR or issue and trace every linked PR, cross-referenced issue, and mention across repos. Use before working an issue/PR to see its whole graph first (the review-full-pr-issue-graph rule); to find orphan, superseded,…
Orchestrate Shaping to decide whether a fix or contributor PR is the right thing to build. Use before implementation when a defect has multiple solution shapes, changes a contract or persistent state, follows a prior review finding, or requires adopting,…
Gate whether a fix or existing contributor PR is the right thing to build. Use before implementation when a defect has multiple solution shapes or changes a contract, especially session state, long-lived process configuration, restart or reuse behavior, fixes…
Gate whether a fix or existing contributor PR is the right thing to build. Use before implementation when a defect has multiple solution shapes or changes a contract, for fixes to prior review findings, and before adopting, absorbing, recreating, or…
Build a minimal, browser-openable before/after artifact that makes a code change, bug fix, feature, benchmark, migration, or visual behavior easy to see and appreciate. Use whenever the user asks for before/after, antes y despues, compare old vs new, show the…
Survey an unfamiliar or shared issue backlog, qualify a small set of worthwhile contributor-side candidates, compare them in an evidence-backed matrix, recommend one, let the user make the final selection, and seed the canonical Issue Contract. Use for…
Escribe el handoff de un ciclo de trabajo en el vault, verificando el estado contra git antes de afirmarlo. Usar al cerrar una sesion larga, antes de compactar, cuando el usuario dice handoff, /handoff, escribi el handoff, donde quedamos, antes de irme, cerra…
Source text: Spanish
Understand, diagnose, change, or review an unfamiliar codebase through one evidence-backed mission. Use when learning architecture, tracing a feature, investigating a bug, implementing a real change with guided or agent execution, reviewing a diff or PR, or…
Candidate: Keep a decision trail (a.k.a. show-your-work) while implementing, so a later reviewer can audit the choices and not just the diff. A TSV appended one row per real decision (what, why, evidence), written in the moment, never reconstructed. Use at…
Record completed or interrupted maintenance work as an evidence ledger. Use after resolving, disproving, reviewing, or investigating an issue, PR, incident, or agent run; when backfilling an old session; or when another skill needs a durable case before…
Prove a performance improvement before and after changing algorithms, data structures, latency, throughput, memory, bundle size, build time, or repeated work. Use when a concrete path is slow or resource-heavy, when considering Map, Set, heap, trie, queue,…
Baseline a repository before quality work. Use when asked to audit maintainability, reliability, performance, security, test quality, technical debt, or code health across a codebase; to identify and rank gaps before fixing them; or to compare quality state…
Candidate: Root-cause a bug you cannot reproduce because it needs another OS or hardware you don't have, by detecting its structural OR visual signature on the machine you DO have. Use whenever you're about to write…