What makes do-issue notable?

1.5K downloads. Trust evidence available

How should do-issue be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

do-issue

Implements GitHub or GitLab issues via parallel subagents with review gates between task batches Skill: do-issue Owner: athola Summary: Implements GitHub or GitLab issues via parallel subagents with review gates between task batches Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:20:02.434Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:40:08.985Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:57:01.762Z | user Release v1.9.16 v1.9.14 | 2026-06-30T18:05:01.720Z | user Release v1.9.14 v1.9.13 | 2026-

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.5k

Updated

Oct 10, 2026

Version

1.9.19

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.5K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.5K downloadsadoption · observed Oct 10, 2026
Latest release: 1.9.19release · observed Aug 26, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-sanctum-do-issue

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-do-issue/snapshot"

Documentation

CLAWHUB

145,974 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: do-issue
description: |
  Implements GitHub or GitLab issues via parallel subagents with review gates between task batches
version: 1.9.8
triggers:
  - github
  - gitlab
  - issues
  - subagents
  - parallel
  - automation
  - cross-platform
  - resolving multi-step issues end-to-end
metadata: {"openclaw": {"homepage": "https://github.com/athola/claude-night-market/tree/master/plugins/sanctum", "emoji": "\u2699\ufe0f", "requires": {"config": ["night-market.leyline:git-platform", "night-market.superpowers:subagent-driven-development", "night-market.superpowers:writing-plans", "night-market.superpowers:test-driven-development", "night-market.superpowers:requesting-code-review", "night-market.superpowers:finishing-a-development-branch"]}}}
source: claude-night-market
source_plugin: sanctum
---

> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.


## Table of Contents

- [Key Features](#key-features)
- [Workflow Overview](#workflow-overview)
- [Required TodoWrite Items](#required-todowrite-items)
- [Configuration](#configuration)
- [Detailed Resources](#detailed-resources)


# Fix Issue(s)

Retrieves issue content from the detected git platform (GitHub, GitLab, or Bitbucket) and uses subagent-driven-development to systematically address requirements, executing tasks in parallel where dependencies allow.

**Platform detection is automatic** via the `leyline:git-platform` SessionStart hook. Check session context for `git_platform:` to determine which CLI to use.

## Key Features

- **Cross-Platform**: Automatically detects GitHub/GitLab/Bitbucket and uses appropriate CLI
- **Flexible Input**: Single issue number, platform URL, or space-delimited list
- **Parallel Execution**: Independent tasks run concurrently via subagents
- **One PR**: All issues produce one consolidated PR (never per-issue PRs)
- **Quality Gates**: Code review between task groups
- **Fresh Context**: Each subagent starts with clean context for focused work

## Workflow Overview

| Phase | Description | Module |
|-------|-------------|--------|
| 1. Discovery | Parse input, fetch issues, extract requirements | [issue-discovery](modules/issue-discovery.md) |
| 2. Planning | Analyze dependencies, create task breakdown | [task-planning](modules/task-planning.md) |
| 3. Execution | Dispatch parallel subagents for independent tasks | [parallel-execution](modules/parallel-execution.md) |
| 4. Quality | Code review gates between task batches | [quality-gates](modules/quality-gates.md) |
| 5-6. Completion | Sequential tasks, final review, issue updates | [completion](modules/completion.md) |

## Required TodoWrite Items

1. `do-issue:discovery-complete`
2. `do-issue:tasks-planned`
3. `do-issue:parallel-batch-complete`
4. `do-issue:review-passed`
5. `do-issue:sequential-complete`
6. `do-issue:issues-up

_meta.json

{
  "ownerId": "kn7d107jg9jv602h9ytsegydq184a42s",
  "slug": "nm-sanctum-do-issue",
  "version": "1.9.19",
  "publishedAt": 1787750402434
}

modules/completion.md

# Phases 5-6: Completion

Execute sequential tasks and finalize the workflow.

## Phase 5: Sequential Tasks

For tasks with dependencies, execute sequentially:

```
Task tool (general-purpose):
  description: "Issue #42 - Task 2: Add login endpoint"
  prompt: |
    You are implementing Task 2 from Issue #42.

    This task depends on completed Task 1 (auth middleware).

    [Task requirements]

    Verify Task 1's middleware works before building on it.
```

Review after each sequential task following the subagent-driven-development pattern.

## Phase 6: Final Review

Dispatch detailed review of all changes:

```
Task tool (superpowers:code-reviewer):
  description: "Final review: Issues #42, #43, #44"
  prompt: |
    Review complete implementation for issues: #42, #43, #44

    Verify:
    - All acceptance criteria met
    - Tests detailed and passing
    - No regressions introduced
    - Code quality meets standards
    - Documentation updated if needed
```

## Update Issue Status

For each completed issue:

```bash
# Add completion comment
gh issue comment 42 --body "Fixed in commit $(git rev-parse --short HEAD)

Changes:
- Implemented auth middleware
- Added login endpoint
- Added detailed tests

Ready for review."

# Optionally close issue
gh issue close 42 --comment "Completed via automated fix workflow"
```

## Pre-PR Consolidation Check

Before creating the PR, verify all work is on ONE branch:

```bash
# Confirm current branch contains all issue commits
git log --oneline --grep="Fixes #42" --grep="Fixes #43" \
  --all-match HEAD
# If commits are on separate branches, cherry-pick or
# rebase them onto the shared branch first.
```

## Finish Development

Use `superpowers:finishing-a-development-branch` to:

- Verify all tests pass
- Present merge options
- Execute chosen completion path

**One PR rule**: Always create exactly ONE pull request
that references all issues via `Fixes #N` lines in
the body. See Step 6.2 in the do-issue command for
the template. Never create separate PRs per issue.

## Tooling Reflection (Night-Market Feedback Loop)

After completing the workflow, reflect on the *tooling itself*
(skills, agents, commands, hooks) rather than the repo code:

- Did any skill behave unexpectedly or have unclear guidance?
- Was a subagent slow, redundant, or missing context?
- Did the do-issue command skip steps or require unnecessary
  manual intervention?
- Did a hook fire incorrectly or miss a case?

**If yes**, post to https://github.com/athola/claude-night-market/discussions
(Learnings category) using the pattern from `fix-pr`
Step 6.7. Always target the night-market repo, not the
current working repo.

**If no observations**, skip this step silently.

> Repo-specific learnings stay in the current repo. Tooling
> learnings always go to
> https://github.com/athola/claude-night-market/discussions
> so the framework can improve.

## Example Final Output

```
Final Review: All requirements met

Issues Summary:
  #42: 3 tasks complet

modules/issue-discovery.md

# Phase 1: Issue Discovery

Parse input arguments and retrieve issue content from the detected git platform. Check session context for `git_platform:` to determine which CLI to use.

## Input Formats

The command accepts flexible input:

```bash
# Single issue number
/do-issue 42

# Platform URL (GitHub or GitLab)
/do-issue https://github.com/owner/repo/issues/42
/do-issue https://gitlab.com/owner/repo/-/issues/42

# Multiple issues (space-delimited)
/do-issue 42 43 44

# Mixed formats
/do-issue 42 https://github.com/owner/repo/issues/43
```

## Retrieve Issue Content

For each issue, fetch the full content using the platform-appropriate CLI:

```bash
# GitHub
gh issue view 42 --json title,body,labels,assignees,comments
gh issue view https://github.com/owner/repo/issues/42 --json title,body,labels,assignees,comments

# GitLab
glab issue view 42
```

## Extract Requirements

From each issue body, identify:

| Category | Look For |
|----------|----------|
| **Acceptance Criteria** | Checkboxes, "should", "must" statements |
| **Technical Requirements** | Code references, API specs, constraints |
| **Test Expectations** | Expected behavior, edge cases |
| **Dependencies** | Related issues, blocking items |

## Example Output

```
Fetching issue #42...
Title: Add user authentication
Requirements identified: 4
  - Acceptance Criteria: 2
  - Technical Requirements: 1
  - Test Expectations: 1
Tasks will be generated: 3
```

## Next Phase

After discovery, proceed to [task-planning.md](task-planning.md) for dependency analysis and task breakdown.

modules/parallel-execution.md

# Phase 3: Parallel Execution

Dispatch subagents for independent tasks concurrently.

## Important: Plan Before Large Dispatch

**When dispatching 4+ agents**, enter plan mode first:

| Agent Count | Requirement |
|-------------|-------------|
| 1-3 agents | Dispatch directly (standard parallel) |
| 4+ agents | **Enter plan mode, write strategy, get user approval, execute** |

### Why This Threshold Exists

Large agent dispatches (4+ agents) create:
- **Observability loss**: Too many concurrent outputs to track
- **Context overflow**: Research agents produce large results, triggering continuation agents that lose state
- **Recovery difficulty**: If 2 of 7 agents fail, there's no plan to resume from
- **Wasted compute**: Without user alignment, agents may research the wrong things

### Plan-Before-Dispatch Checklist

Before launching 4+ agents, your plan should specify:

1. **Agent roster**: Name, type (`general-purpose`/`Explore`/specialized), and model (`sonnet`/`haiku`/`opus`) for each
2. **Scope per agent**: Exactly what each agent investigates (files, topics, questions)
3. **Output contract**: What each agent should return (format, length, key questions to answer)
4. **Result integration**: How you'll combine agent outputs into a coherent response
5. **Failure strategy**: What happens if an agent hits context limits or returns incomplete results

### Example Plan Structure

```markdown
## Agent Dispatch Plan: [Goal]

### Agents (N total)

| # | Agent Type | Model | Scope | Output Contract |
|---|-----------|-------|-------|-----------------|
| 1 | Explore | haiku | Search plugins/ for X | File paths + summaries |
| 2 | general-purpose | sonnet | Research Y via web | Key findings, 500 words max |
| 3 | general-purpose | sonnet | Analyze Z files | Structured assessment |

### Integration Strategy
[How results combine into final answer]

### Failure Handling
- Agent timeout/overflow: [strategy]
- Incomplete results: [strategy]
```

### Enforcement

This rule applies to ALL multi-agent dispatches, including:
- Research/audit missions (web + codebase analysis)
- Large refactoring across many files
- Comprehensive review tasks
- Any task requiring continuation agents

## WARNING: Remote Control / Headless Limitations

**Avoid running parallel subagent dispatches via
`/remote-control` or headless SDK sessions.**

The Task tool blocks the main thread while awaiting
subagent completion. If any subagent hangs (a known
upstream bug), the parent session becomes unrecoverable
because remote-control has no programmatic equivalent
of the `Esc` interrupt.

**Safe alternatives for remote-control use:**
- Use `run_in_background: true` on Agent calls
- Run with `--scope minor` (inline execution, no
  subagent dispatch)
- Use a local terminal with remote-control as a
  monitoring-only window

See [troubleshooting.md](troubleshooting.md) for recovery
steps if a subagent hangs.

## Execute Nonconflicting Tasks in Parallel

**When you have multiple nonconflicting

Github ReposUpdated 17h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.