all publishers

rjmurillo

@rjmurillo source repo

327 published skills · page 4 of 4

  1. ▌
    Security Scan · rjmurillo bundle
    Detect CWE-78 (command injection) regex patterns in Python, PowerShell, Bash, and C# files before PR submission. CWE-22 is delegated to CodeQL; see Scope. Use when you ask "scan for command injection", "CWE-78 check before PR". Do NOT use to decide whether security review is warranted (use security-detection).
    49 repo stars
  2. ▌
    Context Gather · rjmurillo bundle
    Gather comprehensive context from Serena memory, Context7 docs, DeepWiki, and web sources before planning or implementation. Searches across all knowledge tiers and returns a focused summary with a parseable CONTEXT_LOADED marker for downstream skip detection. Use when you say "gather context before planning", "what do we know before I start". Do NOT use for compressing or placing skill text (use context-optimizer).
    49 repo stars
  3. ▌
    Autoplan · rjmurillo
    Route any request to the right skill, command, or agent chain with defaults, so nobody hand-picks from the full catalog. Use when you say `/autoplan`, `do it`, `handle it`, `figure this out`, or when a concrete request names no skill. Do NOT use when the user names a specific skill or lifecycle command; invoke that directly.
    49 repo stars
  4. ▌
    Research · rjmurillo bundle
    Research an external topic, write a 3000-to-5000-word analysis, map it onto this project, and file the follow-up issue. Use when you say `research this topic`, `what does the literature say about X`, or `analyze this external practice for us`. Do NOT use to search this repository (use memory or grep), and do NOT use when no spec, issue, or artifact consumes the result.
    49 repo stars
  5. ▌
    Dx Review · rjmurillo
    Evidence-based developer experience audit. Discovers the target, tests onboarding and setup flows, evaluates API/CLI ergonomics, error messages, documentation, upgrade paths, developer environment, community health, and DX measurement practices. Produces a scorecard where every score cites evidence labeled TESTED, PARTIAL, or INFERRED. Measures Time-to-Hello-World when the target supports it. Compares against a prior dx-review result when one exists (boomerang). Use when asked to "run a DX audit", "test the developer experience", "measure onboarding friction", "DX scorecard", or "evaluate developer ergonomics".
    49 repo stars
  6. ▌
    Pr Review · rjmurillo bundle
    Respond to review comments on one or more pull requests. Clusters the threads, fixes and pushes, then runs the dispatchable completion gate for a verdict. Use when you say `respond to PR review comments`, `pr-review 1234`, or `address the review feedback`. Do NOT use to fix a red check that carries no review comments (use pr-autofix), and do NOT use to work one PR's threads as a step inside another workflow (use pr-comment-responder).
    49 repo stars
  7. ▌
    Adr Review · rjmurillo bundle
    Multi-agent debate orchestration for Architecture Decision Records. Automatically triggers on ADR create/edit/delete. Coordinates architect, critic, independent-thinker, security, analyst, and high-level-advisor agents in structured debate rounds until consensus. Use when you say "review this ADR", when an ADR is created/edited/deleted, or when reviewing, accepting, or updating a decision file under .agents/architecture/, docs/architecture/, docs/decisions/, docs/adr/, or architecture/decisions/, including intent like "review this decision record" or "check this rationale for future maintainers". Do NOT use to author a new ADR (use adr-generator).
    49 repo stars
  8. ▌
    Checkpoint · rjmurillo bundle
    Write a timestamped, secret-redacted snapshot of decisions, progress and next actions to the checkpoints directory, then link it from the active session log. Use when you say `checkpoint this`, `save a recovery point`, or `snapshot where we are` before a risky change or at the end of a working block. Do NOT use to commit or push (it never does either), and do NOT use to write a retrospective (use retro).
    49 repo stars
  9. ▌
    Pr Autofix · rjmurillo
    Fix PRs autonomously. Triage open PRs by tier, address thread feedback, fix CI failures, and enable auto-merge when the 4-condition Ready-to-Merge gate passes. Use when you say `pr-autofix`, `autofix this pr`, or `monitor open prs`. Do NOT use to answer review comments interactively on one PR (use pr-review), and do NOT use to run the six quality axes over your working changes (use pr-quality-all).
    49 repo stars
  10. ▌
    Pre Mortem · rjmurillo bundle
    Guide prospective hindsight analysis to identify project risks before failure occurs. Teams imagine the project has failed spectacularly, then work backward to identify causes. Increases risk identification by 30% compared to traditional planning. Use when you say "run a pre-mortem on", "what could cause this to fail", "identify project risks", or "what could go wrong with". Do NOT use to stress-test a single decision's reasoning (use decision-critic).
    49 repo stars
  11. ▌
    Skillforge · rjmurillo bundle
    Intelligent skill router and creator. Analyzes ANY input to recommend existing skills, improve them, or create new ones. Uses deep iterative analysis with 11 thinking models, regression questioning, evolution lens, and multi-agent synthesis panel. Phase 0 triage ensures you never duplicate existing functionality. Use when you say "create a skill", "do I have a skill for", "which skill should I use", "improve the X skill", or "SkillForge: {goal}". Do NOT use to create a slash command (use slashcommandcreator).
    49 repo stars
  12. ▌
    Codeql Scan · rjmurillo bundle
    Execute CodeQL security scans with language detection, database caching, and SARIF output. Use when performing static security analysis on Python or GitHub Actions code.
    49 repo stars
  13. ▌
    Memory Gate · rjmurillo bundle
    Memory-First Gate (BLOCKING) and the Chesterton's Fence investigation protocol, split out of the memory router per ADR-063. Forces a memory search before you change existing code, constraints, or protocol, so the "why" is recovered before the fence comes down. Use when you say `memory-first gate`, `search memory before changing`, or `chesterton fence check`. Do NOT use for plain Tier 1 lookups (use memory-search) or recording a session (use memory-reflexion).
    49 repo stars
  14. ▌
    Plan · rjmurillo
    Decompose a spec into milestones and atomic tasks with dependency ordering, risk register, and complexity sizing. Use when you say `plan how to build this`, `break this into milestones`, or `decompose this spec`, and run it after spec. Do NOT use to decide what to build (use spec), and do NOT use to write the code (use build).
    49 repo stars
  15. ▌
    Ship · rjmurillo bundle
    Run the four pre-flight checks, then create the PR or validate a contributor branch without touching it. Use when you say `ship it`, `ship this branch`, or `run pre-flight and open the PR`, and run it after review. Do NOT use to open a PR without the gates (use push-pr), and do NOT use to run the review axes themselves (use review).
    49 repo stars
  16. ▌
    Spec · rjmurillo bundle
    Turn a problem into testable requirements with acceptance criteria, through a first-principles gate, a memory-first prior-art gate, and a PRD schema. Use when you say `spec this out`, `what should we build`, or `define the requirements`, and run it before plan. Do NOT use to sequence work into milestones (use plan), do NOT use to write the code (use build), and do NOT use to emit the REQ, DESIGN and TASK files directly (use spec-generator, which this invokes).
    49 repo stars
  17. ▌
    Sync · rjmurillo
    Detect Spec-to-Code drift by scanning REQ, DESIGN and TASK specs for references to code that no longer exists, then report it for triage. Use when you say `detect spec drift`, `sync the specs`, or `did my refactor break a spec`, and run it after a hand-edit that moved or deleted code. Do NOT use to write a spec (use spec), and do NOT use to auto-rewrite specs; it reports and never edits.
    49 repo stars
  18. ▌
    Test · rjmurillo
    Prove a change works across six gates covering functional, non-functional, security, DevOps, developer experience, and observability quality. Use when you say `prove this works`, `run the test gates`, or `validate this change`, and run it after build. Do NOT use to write the implementation or its first tests (use build), and do NOT use to run pre-flight and open a PR (use ship).
    49 repo stars
  19. ▌
    Retro · rjmurillo
    Fill an unfilled auto-retrospective skeleton for a date, or list the skeletons still pending. Use when you say `retro fill`, `fill retro skeleton`, or `list pending retros`. Do NOT use to run the retrospective analysis itself (this hands off to the retrospective skill), and do NOT use to write a session log.
    49 repo stars
  20. ▌
    Github · rjmurillo bundle
    Execute GitHub operations (PRs, issues, milestones, labels, comments, merges) using Python scripts with structured output and error handling. Use when working with pull requests, issues, review comments, CI checks, or milestones instead of raw gh. Use when you say "create a PR", "add label to issue", or "check CI status". Do NOT use to read a pasted github.com URL (use github-url-intercept).
    49 repo stars
  21. ▌
    Memory · rjmurillo bundle
    Thin router for the tiered memory system. Points callers at the focused sub-skills for each operation, Tier 1 search, the reflexion write path, the memory-first gate, maintenance, and consolidation. Use when you ask "what do we know about X", "recall prior context", or "search memory" and are not sure which operation you need. Do NOT use for adding citations (use memory-enhancement) or narrative cross-system reports (use memory-documentary).
    49 repo stars
  22. ▌
    Review · rjmurillo bundle
    Review before merge. Stage-1 spec-compliance gate, then risk-selected Stage-2 review axes from the canonical set. analyst always runs, callers can pin extra always-on axes, and explicit deep review runs the full 16-axis set. Run after /test. Do NOT invoke code-qualities-assessment, doc-accuracy, golden-principles, or taste-lints directly for a full review; review can select them when requested or when deep review is explicit.
    49 repo stars
  23. ▌
    Analyze · rjmurillo bundle
    Systematic multi-step codebase analysis producing prioritized findings with file-line evidence. Covers architecture reviews, security assessments, and code quality evaluations through guided exploration, investigation planning, and synthesis. Use when you say "analyze this codebase", "run security assessment", "architecture review of this system", "find code smells", or "review code quality" across multiple files. Do NOT use for single-file maintainability scoring (use code-qualities-assessment) or CWE-78 injection pattern scanning (use security-scan).
    49 repo stars
  24. ▌
    Metrics · rjmurillo bundle
    Collect agent usage metrics from git history and generate health reports. Use when measuring agent adoption, reviewing system health, or producing periodic dashboards. Collects Invocation Rate, Coverage, Infrastructure Review, and Usage Distribution. Use when you say "collect agent metrics", "generate metrics dashboard", or "weekly metrics report".
    49 repo stars
  25. ▌
    Planner · rjmurillo bundle
    Interactive planning and execution for complex tasks. Use when breaking down multi-step projects (planning) or executing approved plans through delegation (execution). Planning creates milestones with specifications; execution delegates to specialized agents. Use when you say "plan this feature", "create implementation plan", or "resume execution".
    49 repo stars
  26. ▌
    Push Pr · rjmurillo
    Commit the working tree, push the branch, and open a pull request with the repository template filled in from the real diff. Use when you say `push and open a PR`, `open a pull request`, or `push this branch`. Do NOT use to run the pre-ship review gates (use ship), and do NOT use to validate PR metadata alone (use validate-pr-description).
    49 repo stars
  27. ▌
    Reflect · rjmurillo bundle
    CRITICAL learning capture. Extracts HIGH/MED/LOW confidence patterns from conversations to prevent repeating mistakes and preserve what works. Use PROACTIVELY after user corrections ("no", "wrong"), after praise ("perfect", "exactly"), when discovering edge cases, or when skills are heavily used. Without reflection, valuable learnings are LOST forever. Acts as continuous improvement engine for all skills. Invoke EARLY and OFTEN - every correction is a learning opportunity.
    49 repo stars