microboxlabs/gh-issue-writer
.agents/skills/gh-issue-writer/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add microboxlabs/modulariot gh-issue-writerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 8, 2026, 2:22 AM17.4s1 file scanned
SKILL.md
- name:
- gh-issue-writer
- description:
- >
- Use when the user wants to create a feature request (feat:
- ), bug report (bug:),
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:→ labelenhancementbug:→ labelbug- PR URL → inspect the PR with
gh pr view <url> --json title,body,labelsand 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
Related Skills
microboxlabs/miot-calendar
tools
VerifiedTrustedCommunity
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.
4SKILL.mdUpdated Apr 8, 2026
microboxlabs/api-client-sync
tools
VerifiedTrustedCommunity
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".
4SKILL.mdUpdated Apr 8, 2026
microboxlabs/skill-creator
tools
VerifiedTrustedCommunity
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
4SKILL.mdUpdated Apr 8, 2026
microboxlabs/tag-release
tools
VerifiedTrustedCommunity
Tag and release a monorepo package following the project's scoped-tag convention. Use when the user wants to publish a new version of a package, create a release tag, or bump a package version.
4SKILL.mdUpdated Apr 8, 2026