Run any Skill in Manus with one click

$pwd:

implement-issue

Name: Implement Issue
Author: desplega-ai

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

Run Skill in Manus

$ git log --oneline --stat

stars:483

forks:53

updated:April 3, 2026 at 15:37

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

related-skills.json

same repository

agentmail-sending.md

from "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-05-28483

kapso-whatsapp.md

from "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-05-28483

user-management.md

from "desplega-ai/agent-swarm"

How to manage the user registry — creating users for new Slack/GitHub/GitLab/Linear identities, managing aliases, resolving users across platforms. Use when a new human interacts with the swarm or when user identity needs updating.

2026-05-21483

kv-storage.md

from "desplega-ai/agent-swarm"

Use the swarm KV store (Redis-like, namespaced) for cross-task / cross-session / per-page state. Auto-scoped to your context (Slack thread / PR / Linear issue / agent / page). Use for counters, cursors, page state. Do NOT use for secrets (`swarm_config`), embedded knowledge (`memory`), or files (`agent-fs`).

2026-05-13483

artifacts.md

from "desplega-ai/agent-swarm"

Serve interactive web content (HTML pages, dashboards, approval flows, static reports, custom Hono apps) to a public URL via localtunnel. Use when the user asks to "create an artifact for X", "host this for me", "make me a tunneled URL", "spin up a web server for X", "publish this report so I can see it", "share this file/page publicly", "expose this dashboard", "give me a live link", or anything that needs a browser-reachable URL pointing at agent-generated content. Wraps the `agent-swarm artifact` CLI plus the `createArtifactServer` SDK; covers static directories, custom Hono apps, daemonization (nohup / PM2), HTTP Basic auth, and the in-page swarm Browser SDK.

2026-05-12483

swarm-local-e2e.md

from "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-05-06483

package.json

"author": "desplega-ai"

"repository": "desplega-ai/agent-swarm"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

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

implement-issue

Implement Issue

Arguments

Workflow

1. Parse and Fetch

2. Setup

3. Implement

4. Quality Checks, Commit, and Push

5. Create the PR

6. Report Back

Tips

More from this repository

More from this repository

Implement Issue

Arguments

Workflow

1. Parse and Fetch

2. Setup

3. Implement

4. Quality Checks, Commit, and Push

5. Create the PR

6. Report Back

Tips