
Create Issue
- 2 repo stars
- Updated July 24, 2026
- cboone/agent-harness-plugins
Create GitHub issues via tmpfiles to avoid permission prompts from large multiline Bash arguments.
About
Create-issue files GitHub issues through the gh CLI, writing the body via tmpfiles to sidestep permission prompts triggered by large multiline Bash arguments. It makes agent-created issues with long, formatted descriptions reliable. A small project-management/workflow helper for issue tracking.
- Creates GitHub issues via gh
- Uses tmpfiles for large bodies
- Avoids Bash permission prompts
- Clean multiline issue text
Create Issue by the numbers
- Data as of Jul 25, 2026 (Skillselion catalog sync)
/plugin marketplace add cboone/agent-harness-plugins/plugin install create-issue@agent-harness-pluginsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Last updated | July 24, 2026 |
| Repository | cboone/agent-harness-plugins ↗ |
What it does
Create GitHub issues via tmpfiles to avoid permission prompts from large multiline Bash arguments.
README.md
Create Issue
Create GitHub issues using tmpfiles to avoid permission prompts from large multiline Bash arguments.
Type: Skill
Trigger: /create-issue
Installation
See the marketplace install instructions.
What It Does
Creates GitHub issues by writing the issue body to a temporary file and passing it to gh issue create --body-file, instead of inlining large multiline strings as Bash arguments. This keeps the Bash command short and avoids triggering Claude Code's permission prompts for complex commands. Supports labels, assignees, milestones, projects, and cross-repo issue creation.
Requirements
gh. Install via Homebrew:brew install gh
Usage
Ask Claude to create an issue:
- "Create an issue for adding dark mode support"
- "File a bug report about the login timeout"
- "Open an issue on org/repo for the missing docs"
Or invoke directly with /create-issue.
Recommended Permissions
This skill runs GitHub CLI commands that trigger permission prompts. To allow them automatically, add these rules to your .claude/settings.json (project-wide) or ~/.claude/settings.json (global):
{
"permissions": {
"allow": ["Bash(gh issue create *)", "Bash(mktemp /tmp/gh-issue-body-*)", "Bash(rm -f /tmp/gh-issue-body-*)"]
}
}
If you already have a permissions.allow array, merge these entries into it. Review and adjust the rules to match your security preferences.
See Also
- Create Worktree from Issue: Start working on an existing issue in an isolated worktree
- Suggest Next Issue: Get recommendations on which issue to tackle next
- All plugins