How do I install the Gh Issue Writer skill?

Run npx skillmds@latest add microboxlabs/gh-issue-writer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gh Issue Writer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh Issue Writer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gh Issue Writer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gh Issue Writer?

microboxlabs (@microboxlabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gh Issue Writer by microboxlabs — Agent Skill

Name: Gh Issue Writer
Author: microboxlabs

Gh Issue Writer

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.

microboxlabs dff187c 3.4 KB Updated Sep 17, 2026

File contents

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

---name: gh-issue-writerdescription: 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.---# GitHub Issue WriterCreate GitHub issues with project board integration and development branch setup.## Workflow1. Parse input (type + description or PR URL)2. Create the issue via `gh issue create`3. Add issue to project board and capture item ID4. Set project status5. Create and checkout development branch## Step 1: Parse InputDetermine 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 + descriptionExtract a concise title and body from the user input or PR.## Step 2: Create the IssueLoad config and publish:```bashsource .env.localgh 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```bashsource .env.localITEM_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```bashsource .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```bashsource .env.localgh 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:```bashgit fetch origin && git checkout "based/<ISSUE_NUMBER>-<short-name>"```## Environment VariablesAll 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:```bashsource .env.localgh project list --owner "$GH_PROJECT_OWNER" --format json | jq '.projects[] | select(.number == <N>)'gh project field-list <N> --owner "$GH_PROJECT_OWNER" --format json```

Frequently asked questions