Draft pull-request creation workflow. Use when repositories have pending changes or unpushed commits and you want draft PRs created.
RooCodeInc/Roomote
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 49
- GitHub stars
- 345
- GitHub forks
- 60
Install with an AI assistant
Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/RooCodeInc/Roomote.Loading the repository README…
Skills in this repository
Showing 40 of 49 collected skills.
Inline code review workflow. Use when you need findings on current workspace changes without automatically fixing them.
Decide whether browser proof applies to a shipped change, capture screenshots or screencasts directly with agent-browser, upload them, and return an honest proof result for the parent workflow and the judge.
Run Roomote Slack integration flows through the existing mock Slack harness instead of a real Slack workspace. Use when testing Slack app mentions, interactive payloads, URL verification, outbound Slack posts, deleted-thread suppression,…
Try one narrowly scoped Jevgrep (jg) search for unfamiliar code, with a 30-second limit, then use ordinary code search.
Add a new built-in MCP integration to Roomote. Use when adding a new third-party service (e.g. Asana, Datadog, Vercel) to the built-in integrations catalog shown on the Integrations page.
Produce a polished demo video of a product feature — recorded live in the sandbox browser with cursor effects, captions, and optional voice-over narration.
Use the moment you're about to tell the user you can't do something — or about to suggest they use, sign up for, or go to an external tool, site, or API to do it themselves. Commonly that means things outside a model's native abilities: generating images,…
End-to-end repository implementation workflow. Use when the request requires changing code, with repository-grounded analysis, correct edits, proportional validation, and profile-aware branch/push/PR behavior.
Internal skill to configure environments. Never use unless the user explicitly initiates the skill. Focus on localhost-ready setup and validation.
Review current open CodeQL / GitHub code-scanning alerts with GitHub data, keep scheduled runs read-only, and submit a small set of environment-backed `act` work items that auto-start remediation execution tasks.
Automation skill: per-issue Sentry remediation workflow. Use when a Roomote task is asked to investigate a specific Sentry issue (typically posted into Slack), produce a fix or evidence-backed recommendation, and report the outcome clearly.
Automation skill: Better Stack observability triage workflow. Use when a task should periodically scan Roomote Better Stack logs, warnings, errors, uptime checks, incidents, and telemetry via the Better Stack MCP and identify actionable operational chores.
Guidelines and canonical patterns for building UI in the Roomote web application. Use when creating new pages, components, dialogs, forms, or modifying existing UI in `apps/web/`.
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for…
Help a person identify worthwhile specific work Roomote could take on and decide whether to try a small, bounded experiment.
Prepare Roomote releases: cut the normal release PR from develop, or ship an urgent patch directly from latest main and synchronize its version back to develop. Use when asked to prep, cut, hotfix, or write notes for a release.
Repository-agnostic dependency maintenance workflow. Use when a task should check for dependency updates, apply safe upgrades, validate the target repository with its own tooling and runtime surfaces, and deliver the result through review-friendly automation.
Fast-only environment-health orchestration workflow. Launch a fresh Roomote task from Fast against the target environment, assess its startup and requested journey, classify ownership, delegate only authorized repairs, and verify again.
Run Roomote email (AgentMail) integration flows through the checked-in mock AgentMail API harness instead of the real AgentMail service. Use when testing email task entry, inbox provisioning, webhook registration, Svix-signed `message.received` deliveries,…
Pull-request feedback fixer workflow. Use when you need to implement fixes requested on an existing pull request from review threads, fix-id links, top-level PR comments, or broad "fix all unresolved issues" requests.
Run Sentry triage for the requested scope using available capabilities. Keep scans read-only, rank actionable findings, and follow the supplied reporting and follow-up requirements.
Automation skill: Scan Sentry issues, errors, regressions, and alerts within the requested scope, then rank code or instrumentation follow-up work.
Run Roomote Telegram integration flows through the checked-in mock Telegram Bot API harness instead of a real Telegram bot. Use when testing Telegram task entry, follow-up queueing to active jobs, the `/new` command, callback buttons, outbound Telegram posts,…
Pull-request creation workflow. Use when repositories have pending changes or unpushed commits and you want ready-for-review PRs created.
Review current open Dependabot alerts with GitHub data, keep scheduled runs read-only, and submit a small set of environment-backed `act` work items that auto-start dependency-update execution tasks.
Run Roomote Discord integration flows through the checked-in mock Discord REST harness and synthetic Gateway envelopes instead of a real Discord bot. Use when testing Discord task entry, follow-up queueing to active jobs, slash commands (`/new`, `/goal`,…
General workflow for answering questions, investigating evidence, and performing exact user-requested actions outside repository implementation work.
Manage repository labels, milestones, and GitHub Projects V2 safely through the scoped GitHub App credential. Use for requests to list, create, edit, delete, assign, or move GitHub management resources.
Automation skill: review recently merged pull requests for high-confidence code quality issues and submit `act` work items that auto-start follow-up execution tasks.
Automation skill: run a broad refactor survey across the codebase, rank candidates by leverage, and produce standalone plans for the top opportunities without auto-implementing them.
Automation skill: review recently merged pull requests for concrete security issues and secure-by-default gaps, then submit actionable `act` work items that auto-start follow-up execution tasks.
Investigate the latest default-branch CI failure in an environment-backed workspace and, when it is real and fixable, fix and open a PR in the same task.
Investigate a specific open source-control issue and post either clarifying questions or a concrete implementation plan on the issue without implementing code or opening a PR.
Focused GitHub PR-feedback workflow for addressing unresolved review threads on the current pull request.
Resolve GitHub pull-request merge conflicts by merging the base branch into the PR branch, applying intent-aware conflict resolution, and running an integrated safety review before the merge commit is finalized.
Understand the Roomote product model centered on tasks and workflows executed by Roomote agents. Use when working in the Roomote repo on product framing, onboarding, routing, integrations, UI, or docs where workflow, runtime dispatch, behavior mode, and…
Trace how Roomote agents run through the Roomote runtime and integrations. Use when debugging or changing controller/worker/queue behavior, preview proxy flows, snapshots, MCP setup, or Slack/Linear/GitHub entry points that create or resume Roomote agent work.
Identify and optionally close stale GitHub pull requests using `gh`, with dry-run support and a configurable exempt label. Use when asked to clean stale PRs, close inactive PRs, or run PR hygiene.
Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI.