Run any Skill in Manus with one click

gh-issue-writer

Stars4

Forks3

UpdatedApril 6, 2026 at 23:44

Create and publish GitHub issues with full project board integration. Use when the user wants to create a feature request (feat:), bug report (bug:), or any tracked issue from a PR or description. Handles issue creation, project board association, status setting, and development branch checkout. Also use when the user says "create an issue", "write an issue for this PR", "track this work", or provides a PR URL to turn into an issue.

Installation

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.

Run Skill in Manus

Source

microboxlabs

microboxlabs/modulariot

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name

gh-issue-writer

description

GitHub Issue Writer

Create GitHub issues with project board integration and development branch setup.

Workflow

Parse input (type + description or PR URL)
Create the issue via gh issue create
Add issue to project board and capture item ID
Set project status
Create and checkout development branch

Step 1: Parse Input

Determine issue type from prefix or context:

feat: → label enhancement
bug: → label bug
PR URL → inspect the PR with gh pr view <url> --json title,body,labels and derive type + description

Extract a concise title and body from the user input or PR.

Step 2: Create the Issue

Load config and publish:

source .env.local

gh issue create \
  --repo "$GH_ISSUE_REPO" \
  --title "<title>" \
  --body "<body>" \
  --label "<labels>"

Capture the issue number from the output.

Step 3: Add to Project Board

source .env.local

ITEM_ID=$(gh project item-add "$GH_PROJECT_NUMBER" \
  --owner "$GH_PROJECT_OWNER" \
  --url "https://github.com/$GH_ISSUE_REPO/issues/<ISSUE_NUMBER>" \
  --format json | jq -r '.id')

Step 4: Set Project Status

source .env.local

# If files are already modified locally → "In Progress"
gh project item-edit \
  --project-id "$GH_PROJECT_ID" \
  --id "$ITEM_ID" \
  --field-id "$GH_STATUS_FIELD_ID" \
  --single-select-option-id "$GH_STATUS_IN_PROGRESS"

# Otherwise → "Ready for Development"
gh project item-edit \
  --project-id "$GH_PROJECT_ID" \
  --id "$ITEM_ID" \
  --field-id "$GH_STATUS_FIELD_ID" \
  --single-select-option-id "$GH_STATUS_READY_FOR_DEV"

Step 5: Create Development Branch

source .env.local

gh issue develop <ISSUE_NUMBER> \
  --repo "$GH_ISSUE_REPO" \
  --branch-repo "$GH_ISSUE_REPO" \
  --base trunk \
  --name "based/<ISSUE_NUMBER>-<short-name>" \
  --checkout

Branch naming: based/<issue-number>-<3-4-word-slug>

If --checkout fails due to local changes:

git fetch origin && git checkout "based/<ISSUE_NUMBER>-<short-name>"

Environment Variables

All values are read from .env.local (not committed to git):

Variable	Example	Purpose
`GH_PROJECT_OWNER`	`microboxlabs`	Org or user
`GH_ISSUE_REPO`	`microboxlabs/modulariot`	Target repo
`GH_PROJECT_NUMBER`	`4`	Project board number
`GH_PROJECT_ID`	`PVT_...`	Project node ID
`GH_STATUS_FIELD_ID`	`PVTSSF_...`	Status field ID
`GH_STATUS_BACKLOG`	option ID	Backlog status
`GH_STATUS_READY_FOR_DEV`	option ID	Ready for Dev status
`GH_STATUS_IN_PROGRESS`	option ID	In Progress status
`GH_STATUS_IN_REVIEW`	option ID	In Review status
`GH_STATUS_DONE`	option ID	Done status

To discover these values:

source .env.local
gh project list --owner "$GH_PROJECT_OWNER" --format json | jq '.projects[] | select(.number == <N>)'
gh project field-list <N> --owner "$GH_PROJECT_OWNER" --format json

More from this repository

same repository

miot-search

microboxlabs/modulariot

Resolve a free-text query typed into the ModularIoT app search box into a direct answer, a deep link to the right page, or a build request. Use when the user searches for a page or section, looks up an entity (truck, trailer, driver, task, service, expedition, booking, conversation), or asks a data question from the spotlight search.

2026-07-094

goal-loop

microboxlabs/modulariot

Drive a long, multi-stage objective to completion with the Claude Code `/goal` plugin — a Ralph-style autonomous workflow built on `/goal`'s single-condition evaluator loop instead of `/loop`+ScheduleWakeup. Use when the user wants to "drive a goal", "goal ladder", "ralph with /goal", "run the goal loop", "autonomous goal", or hands you a multi-phase brief to be executed via `/goal`. Bootstraps a goal ladder if none exists; otherwise resumes from `GOAL-LADDER.md`. For the ScheduleWakeup-based variant, use `plan-loop` instead.

2026-05-254

plan-loop

microboxlabs/modulariot

Drive a long, multi-task plan to completion via `/loop` + `ScheduleWakeup` + `Monitor` — a Ralph-style autonomous workflow that does NOT require the ralph-loop plugin. Use when the user wants to "drive a plan", "run a worklist autonomously", "iterate through phased tasks", "ralph-style loop", "long autonomous plan", or hands you a multi-phase brief that will take several hours and dozens of small commits to complete. Bootstraps a plan directory if none exists. Otherwise resumes from `RALPH-WORKLIST.md`.

2026-05-104

api-client-sync

microboxlabs/modulariot

Propagate OpenAPI spec changes through all three layers: (1) the hand-authored TypeScript client package — types, resource methods, tests, version bump; (2) the CLI package — commands, flags, table columns, tests, version bump; (3) the agent skill — SKILL.md workflows, business rules, and reference.md sections. Use when the user says the openapi.json has changed and needs to be reflected end-to-end. Triggers on phrases like "update the client from the new openapi", "sync the client with the API spec", "implement the api changes in the client", "the openapi.json changed, update the client package", "propagate the API changes", or "update all layers from the spec".

2026-05-084

miot-calendar

microboxlabs/modulariot

Query and manage ModularIoT Calendar services via the miot CLI. List calendars, check slot availability, create bookings, manage time windows, and run slot managers. Use when the user asks about schedules, appointments, bookings, availability, calendar configuration, time slots, capacity, or calendar services in their ModularIoT organization.

2026-05-084

mintral-design-system

microboxlabs/modulariot

Design system for Mintral — "Logística Minera", a mining-logistics control-tower web app built by MicroBoxLabs. Covers the brand (yellow + slate wordmark), Flowbite-blue product UI, Spanish/English dispatcher copy voice, and the 8-column shipping kanban workflow (driver validation → mission control → Sovos signature → monitoring → delivery → finalized). Invoke when designing anything in the Mintral product surface (kanban, trip cards, sidebar, drawer, login), the MicroBoxLabs marketing site, or any operator UI that shares this vocabulary (torre de control, faena, overlord, código negro).

2026-05-074

name

gh-issue-writer

description

GitHub Issue Writer

Create GitHub issues with project board integration and development branch setup.

Workflow

Parse input (type + description or PR URL)
Create the issue via gh issue create
Add issue to project board and capture item ID
Set project status
Create and checkout development branch

Step 1: Parse Input

Determine issue type from prefix or context:

feat: → label enhancement
bug: → label bug
PR URL → inspect the PR with gh pr view <url> --json title,body,labels and derive type + description

Extract a concise title and body from the user input or PR.

Step 2: Create the Issue

Load config and publish:

source .env.local

gh issue create \
  --repo "$GH_ISSUE_REPO" \
  --title "<title>" \
  --body "<body>" \
  --label "<labels>"

Capture the issue number from the output.

Step 3: Add to Project Board

source .env.local

ITEM_ID=$(gh project item-add "$GH_PROJECT_NUMBER" \
  --owner "$GH_PROJECT_OWNER" \
  --url "https://github.com/$GH_ISSUE_REPO/issues/<ISSUE_NUMBER>" \
  --format json | jq -r '.id')

Step 4: Set Project Status

source .env.local

# If files are already modified locally → "In Progress"
gh project item-edit \
  --project-id "$GH_PROJECT_ID" \
  --id "$ITEM_ID" \
  --field-id "$GH_STATUS_FIELD_ID" \
  --single-select-option-id "$GH_STATUS_IN_PROGRESS"

# Otherwise → "Ready for Development"
gh project item-edit \
  --project-id "$GH_PROJECT_ID" \
  --id "$ITEM_ID" \
  --field-id "$GH_STATUS_FIELD_ID" \
  --single-select-option-id "$GH_STATUS_READY_FOR_DEV"

Step 5: Create Development Branch

source .env.local

gh issue develop <ISSUE_NUMBER> \
  --repo "$GH_ISSUE_REPO" \
  --branch-repo "$GH_ISSUE_REPO" \
  --base trunk \
  --name "based/<ISSUE_NUMBER>-<short-name>" \
  --checkout

Branch naming: based/<issue-number>-<3-4-word-slug>

If --checkout fails due to local changes:

git fetch origin && git checkout "based/<ISSUE_NUMBER>-<short-name>"

Environment Variables

All values are read from .env.local (not committed to git):

Variable	Example	Purpose
`GH_PROJECT_OWNER`	`microboxlabs`	Org or user
`GH_ISSUE_REPO`	`microboxlabs/modulariot`	Target repo
`GH_PROJECT_NUMBER`	`4`	Project board number
`GH_PROJECT_ID`	`PVT_...`	Project node ID
`GH_STATUS_FIELD_ID`	`PVTSSF_...`	Status field ID
`GH_STATUS_BACKLOG`	option ID	Backlog status
`GH_STATUS_READY_FOR_DEV`	option ID	Ready for Dev status
`GH_STATUS_IN_PROGRESS`	option ID	In Progress status
`GH_STATUS_IN_REVIEW`	option ID	In Review status
`GH_STATUS_DONE`	option ID	Done status

To discover these values:

source .env.local
gh project list --owner "$GH_PROJECT_OWNER" --format json | jq '.projects[] | select(.number == <N>)'
gh project field-list <N> --owner "$GH_PROJECT_OWNER" --format json