rohaquinlop
- 19 skills
- 0 followers
- 6 hours ago last updated
- ▌
- ▌ Bridge Builder Delegate · rohaquinlopDelegate implementation work to the bridge-builder MCP server. Use when a request should be executed by the bridge-builder pipeline instead of being implemented directly in the current Codex thread.
- ▌ Redes Sociales · rohaquinlopExtraer datos verificables (acopios, jornadas de sangre, albergues, anuncios oficiales) de publicaciones en redes sociales — X, Instagram, Facebook, WhatsApp, Telegram — para el proyecto enlace-sismo. Usar cuando el usuario comparte links de posts o capturas de pantalla con información humanitaria, o pide buscar anuncios oficiales de alcaldías/entidades en redes.
- ▌ Create Issue · rohaquinlopCreate a well-formed GitHub issue with a clean title and body. Invoke whenever the user asks to create an issue, file a bug report, open a feature request, or report something via GitHub CLI. Encodes the lessons learned from bad issue drafts: GitHub renders every single newline as a hard line break, internal working-doc jargon does not belong in public issues, and titles must match the repo's existing conventions.
- ▌ Apply · rohaquinlopImplement a change's tasks.md against real code, checking off tasks as they complete. Use once a change has been proposed. Optionally takes a change name as an argument, e.g. "/sdd:apply add-dark-mode".
- ▌ Archive · rohaquinlopArchive a completed change once all its tasks are done, folding its spec deltas into the project's main specs/. Optionally takes a change name as an argument, e.g. "/sdd:archive add-dark-mode".
- ▌ Explore · rohaquinlopThinking partner for investigating an idea or problem before committing to structured spec work. Use before /sdd:propose when the user wants to discuss options, not yet produce artifacts.
- ▌ Propose · rohaquinlopCreate a new spec-driven change with proposal, design, tasks, and spec artifacts. Use when the user is ready to commit to a direction for a feature or fix. Takes the change name/idea as an argument, e.g. "/sdd:propose add-dark-mode".
- ▌ Init · rohaquinlopScan a project and generate or update an AGENTS.md file with project conventions, tech stack, build/test/lint commands, structure, and coding style. Use when setting up a new project for AI agent assistance, or when the user asks to create, update, or regenerate an AGENTS.md or CLAUDE.md context file.
- ▌ Inline Review · rohaquinlopReview a GitHub PR and post inline review comments using the gh extension `gh-inline-review-comments`. Generates a `pr-<N>-review-comments.md` file with ordered findings, then posts them as one review (comment / approve / request-changes). Invoke when the user asks to add inline review comments, review a PR with line comments, re-request changes, or regenerate/post a PR review-comments file.
- ▌ Release Notes · rohaquinlopGenerate polished release notes for a new version by inspecting git history and past release formats. Supports creating the git tag and publishing the release via `gh release create`. Invoke when the user asks to write release notes, publish a release, or draft a changelog entry for a new version.
- ▌ Plan Clarifier · rohaquinlopReviews an existing implementation plan from an MD file, pasted text, issue, comment, or rough idea; detects missing context; asks targeted multiple-choice clarification questions with recommended answers first; supports custom authored answers, dig-deeper follow-ups, and delegation when the user says to decide. Use before implementing unclear features, refactors, migrations, or tasks needing better context.
- ▌
- ▌
- ▌ Handoff · rohaquinlopCompact the current conversation into a handoff document for another agent to pick up.
- ▌ Create Pr · rohaquinlopCreate a GitHub Pull Request, or write a PR description, with title/body generated from the git diff. Supports optional target branch (defaults to main). MUST be loaded before creating or writing a PR description. Invoke whenever the user asks to create a PR, open a pull request, summarize branch changes, or submit changes via GitHub CLI.
- ▌ Git Commit · rohaquinlopCommit message conventions and git commit execution rules. MUST be loaded before running any git commit command. Invoke whenever the user asks to commit changes, stage files, or create a commit — even without an explicit slash command.
- ▌ System Map · rohaquinlop bundleTurn a codebase, a set of services, a change, or a runtime path into an interactive isometric system map you can point at and discuss. Works across one repo or many in a workspace, and can be seeded from architecture notes, design docs, a README or CLAUDE.md, or context given in conversation. Language- and stack-agnostic. Use when the user wants to understand how a repo is put together, how services interact, what a PR or commit range actually touched, or what happens along one entry point. Triggers on "map this repo", "system map", "map these services", "how does this fit together", "visualize the architecture", "show me what this PR changed", "trace this request", "explain this codebase visually".
- ▌ Poc Codebase Review · rohaquinlopReview a codebase implementation against the PoC it was based on. Use when validating PR comments, behavior claims, parity gaps, regressions, or implementation differences between a production/service codebase and a proof-of-concept file, pipeline, notebook, or reference implementation. The user may provide PoC paths, a main entry point, target functions, reviewer comments, or domain notes.