Menu
Implement a GitHub issue or GitLab issue and create a PR/MR
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | implement-issue |
| description | Implement a GitHub issue or GitLab issue and create a PR/MR |
Read a GitHub or GitLab issue, implement the requested changes, and create a PR/MR.
Provider detection: Check the URL or remote:
gh issue view / gh pr createglab issue view / glab mr createissue-number-or-url: Either an issue number (e.g., 123) or a full URLIf given a URL, extract owner, repo, and issue number. Fetch issue details (title, body, labels, comments). Understand what's being requested, acceptance criteria, and any technical constraints.
/workspace/personal/<repo-name> (clone with gh repo clone if needed)fix/issue-<number>-<short-description>Keep changes focused on what the issue requests. Avoid scope creep.
Fix #123: <description>). Use conventional commit style if the repo uses it.git push -u origin HEAD.Create the PR with a descriptive title and body including: summary of changes, key changes list, testing done, and Fixes #<issue-number> to auto-close the issue on merge.
After creating the PR, check CI status with gh pr checks (GitHub) or glab mr view --json pipelines (GitLab). If CI fails, fix the issues, push, and re-check until green.
Provide the PR URL, summary of changes, and any caveats. Optionally comment on the original issue linking the PR.
/skill:respond-github to ask for clarificationUse swarm scripts for bulk SDK calls, repetitive fan-out, and context-efficient data processing.
Fetch a file attached to your current task in ONE call. Use whenever a task carries an attachment (an image, PDF, or other file the requester uploaded) and you need its bytes on disk — the dispatch prompt lists attachments with a ready-to-run curl command, but if you're improvising (resumed session, follow-up task, or the recipe scrolled out of context) use this skill instead of reaching for the `agent-fs` CLI directly.
Guide for running local E2E tests with API server, Docker lead/worker containers, task creation, log verification, UI dashboard, and cleanup
Canonical AgentMail send-message API reference for swarm agents. Pins the base URL, required field names, text-only rendering workaround, BCC policy, and ready-to-copy curl / swarm-script examples so agents do not rediscover the API surface at runtime.
How to interact with Kapso WhatsApp from the swarm — read inbound webhook payloads (text AND media), fetch message history, send free-form messages within the 24h session window (and template messages outside it), mark-as-read, show the typing indicator, send reactions, download media, verify webhook signatures, and resolve contacts to swarm users. Canonical reference for ANY Kapso interaction beyond the thin `send-whatsapp-message` / `reply-whatsapp-message` MCP tools — for templates, media, reactions, typing, mark-as-read, signature verify, contact resolution, conversation history, drop to the REST recipes here. Use whenever a task references a WhatsApp message routed through Kapso, or when a workflow needs to reply on WhatsApp.
Per-app playbook for driving Gmail through Composio (toolkit slug `gmail`). Verified GMAIL_* tool slugs and argument shapes for reading, searching, sending, drafts, labels, and threads. Use alongside the `composio` hub skill whenever a task reads or sends Gmail for a connected user. Covers the metadata-first reads, the GMAIL_SEND_EMAIL HTML flag, and reply-to-thread.