Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

implement-issue

Estrelas588

Forks67

Atualizado3 de abril de 2026 às 15:37

Implement a GitHub issue or GitLab issue and create a PR/MR

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

desplega-ai

desplega-ai/agent-swarm

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	implement-issue
description	Implement a GitHub issue or GitLab issue and create a PR/MR

Implement Issue

Read a GitHub or GitLab issue, implement the requested changes, and create a PR/MR.

Provider detection: Check the URL or remote:

If GitHub → use gh issue view / gh pr create
If GitLab → use glab issue view / glab mr create

Arguments

issue-number-or-url: Either an issue number (e.g., 123) or a full URL

Workflow

1. Parse and Fetch

If 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.

2. Setup

Ensure repo is cloned to /workspace/personal/<repo-name> (clone with gh repo clone if needed)
Fetch origin, checkout main, pull latest
Create a feature branch: fix/issue-<number>-<short-description>

3. Implement

Understand the codebase — explore relevant files and existing patterns
Plan your approach — consider using plan creation for complex changes
Write the code — implement the requested functionality
Test your changes — run existing tests, add new tests if appropriate
Verify it works — manual verification where possible

Keep changes focused on what the issue requests. Avoid scope creep.

4. Quality Checks, Commit, and Push

Run PR checks (MANDATORY) — Run ALL checks from the "PR Checks" section of your Repository Guidelines. Fix any failures before proceeding. If no guidelines are defined, check the project's CLAUDE.md for a pre-PR checklist.
Commit with a message referencing the issue (e.g., Fix #123: <description>). Use conventional commit style if the repo uses it.
Push with git push -u origin HEAD.

5. Create the PR

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.

6. Report Back

Provide the PR URL, summary of changes, and any caveats. Optionally comment on the original issue linking the PR.

Tips

Read the issue thoroughly before starting — misunderstanding wastes time
Check for related issues or existing PRs
One issue = one PR
If the issue is too large, break it into smaller PRs
If unclear, use /skill:respond-github to ask for clarification

Mais deste repositório

mesmo repositório

swarm-scripts

desplega-ai/agent-swarm

Use swarm scripts for bulk SDK calls, repetitive fan-out, and context-efficient data processing.

2026-07-09588

download-task-attachment

desplega-ai/agent-swarm

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.

2026-07-03588

swarm-local-e2e

desplega-ai/agent-swarm

Guide for running local E2E tests with API server, Docker lead/worker containers, task creation, log verification, UI dashboard, and cleanup

2026-07-02588

agentmail-sending

desplega-ai/agent-swarm

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.

2026-06-05588

kapso-whatsapp

desplega-ai/agent-swarm

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.

2026-06-05588

composio-gmail

desplega-ai/agent-swarm

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.

2026-06-02588

name	implement-issue
description	Implement a GitHub issue or GitLab issue and create a PR/MR

Implement Issue

Read a GitHub or GitLab issue, implement the requested changes, and create a PR/MR.

Provider detection: Check the URL or remote:

If GitHub → use gh issue view / gh pr create
If GitLab → use glab issue view / glab mr create

Arguments

issue-number-or-url: Either an issue number (e.g., 123) or a full URL

Workflow

1. Parse and Fetch

If 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.

2. Setup

Ensure repo is cloned to /workspace/personal/<repo-name> (clone with gh repo clone if needed)
Fetch origin, checkout main, pull latest
Create a feature branch: fix/issue-<number>-<short-description>

3. Implement

Understand the codebase — explore relevant files and existing patterns
Plan your approach — consider using plan creation for complex changes
Write the code — implement the requested functionality
Test your changes — run existing tests, add new tests if appropriate
Verify it works — manual verification where possible

Keep changes focused on what the issue requests. Avoid scope creep.

4. Quality Checks, Commit, and Push

Run PR checks (MANDATORY) — Run ALL checks from the "PR Checks" section of your Repository Guidelines. Fix any failures before proceeding. If no guidelines are defined, check the project's CLAUDE.md for a pre-PR checklist.
Commit with a message referencing the issue (e.g., Fix #123: <description>). Use conventional commit style if the repo uses it.
Push with git push -u origin HEAD.

5. Create the PR

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.

6. Report Back

Provide the PR URL, summary of changes, and any caveats. Optionally comment on the original issue linking the PR.

Tips

Read the issue thoroughly before starting — misunderstanding wastes time
Check for related issues or existing PRs
One issue = one PR
If the issue is too large, break it into smaller PRs
If unclear, use /skill:respond-github to ask for clarification