gh-issue-edit
npx machina-cli add skill dceoy/github-cli-agent-skills/gh-issue-edit --openclawFiles (1)
SKILL.md
1.3 KB
GitHub Issue Edit
When to use
- The user asks to update issue metadata or content.
- You need to add/remove labels, assignees, milestones, or projects.
Inputs to confirm
- Issue number(s) or URL(s).
- Changes to apply (title/body/labels/etc.).
- Target repo if not current (
--repo OWNER/REPO).
Workflow
- Verify auth:
gh --version gh auth status - Apply edits:
gh issue edit 123 --title "New title" --body "Updated body" gh issue edit 123 --add-label "bug" --remove-label "triage" gh issue edit 123 --add-assignee "@me" - Verify:
gh issue view 123
Examples
# Add labels and assign yourself
~ gh issue edit 123 --add-label "help wanted" --add-assignee "@me"
Notes
--add-assignee/--remove-assigneesupport@meand@copilot(GitHub.com only).- Project edits may require
gh auth refresh -s project.
References
- GitHub CLI manual: https://cli.github.com/manual/
gh issue edit --help
Source
git clone https://github.com/dceoy/github-cli-agent-skills/blob/main/skills/gh-issue-edit/SKILL.mdView on GitHub Overview
gh-issue-edit enables updating issue metadata and content directly from the command line. You can modify titles, bodies, labels, assignees, milestones, and project associations without opening the GitHub UI. This streamlines issue triage and project management across repos.
How This Skill Works
Authenticate with gh, then run gh issue edit with the desired flags to modify title, body, labels, assignees, milestones, or projects. After applying changes, verify the result with gh issue view to ensure accuracy.
When to Use It
- You need to update issue metadata (labels, assignees, milestones, projects).
- You want to adjust the issue title or body for clarity or status.
- Working across multiple repositories and need to specify --repo.
- Batch edits like adding/removing multiple labels or assignees.
- You want to verify changes immediately by viewing the issue.
Quick Start
- Step 1: Verify auth by running gh --version and gh auth status
- Step 2: Apply edits with gh issue edit <ISSUE> [flags] to modify title/body/labels/assignees/milestones/projects
- Step 3: Verify the result with gh issue view <ISSUE>
Best Practices
- Confirm the issue number or URL and target repo before editing.
- Prefer incremental edits (add/remove) rather than overwriting with a single --title/--body change.
- Use --repo when you are editing issues outside the current repository.
- Validate changes with gh issue view after applying edits.
- Be mindful of assignee and project constraints (e.g., @me and @copilot on GitHub.com; project edits may require gh auth refresh -s project).
Example Use Cases
- gh issue edit 123 --add-label 'help wanted' --add-assignee '@me'
- gh issue edit 123 --title 'New title' --body 'Updated body'
- gh issue edit 123 --remove-label 'triage' --add-label 'bug'
- gh issue edit 123 --milestone 'Sprint-5'
- gh issue edit 123 --add-label 'enhancement' --milestone 'Q3'
Frequently Asked Questions
Add this skill to your agents