Language Conventions
Infer language style from the project:
- Analyze existing issues, documentation, and commit messages to detect the project's language variant (US English, UK English, etc.)
- Match the spelling conventions found in the project (e.g., "initialize" vs "initialise", "behavior" vs "behaviour")
- Maintain consistency with the project's established language style throughout issue updates
Update a GitHub issue with the following workflow:
- Check if we're in a GitHub repository
- Identify the issue to update:
- If issue number is provided (e.g., "issue 123", "#456", or "789"), use that issue
- If not provided, ask the user for the issue number
- View current issue details:
- Use
gh issue view to display current state
- Show title, body, labels, assignees, and state
- This helps understand what needs updating
- Check for ISSUE_TEMPLATE format:
- Look for issue templates in
.github/ISSUE_TEMPLATE/ or .github/ directories
- If the current issue follows a template, identify which template
- Parse template structure to preserve required sections
- Determine what to update:
- Ask what fields the user wants to update (title, body, labels, assignees, state)
- Accept input for new values
- If updating body and template exists, maintain template structure
- Apply updates with validation:
- For title: Use natural, descriptive language
- For body with template: Preserve template sections and formatting
- For body without template: Use clear, structured format
- For labels: Only use existing repository labels
- For assignees: Only assign valid repository collaborators
- Use
gh issue edit to apply changes
- Confirm and display results:
- Show summary of all updates made
- Display success message with link to updated issue
For the issue title:
- Use natural, descriptive language
- Keep it concise but informative
- Match the style of existing issue titles in the repository
For the issue body (when using ISSUE_TEMPLATE format):
- Follow the exact template structure
- Preserve required sections and formatting
- Update only the sections being changed
- Maintain template sections
For the issue body (custom format):
- Include clear problem statement or feature details
- Add relevant context from the update
- Keep it structured and actionable
- Maintain existing formatting style when possible
For labels and assignees:
- Only add labels that already exist in the repository
- Validate assignees are valid repository collaborators
- Show current labels and assignees before making changes
1---
2name: update-issue
3description: Update a GitHub issue with new title, body, labels, or assignees
4allowed-tools: Bash(gh issue view) Bash(gh issue edit) Bash(gh repo view)
5metadata:
6 source: https://skillmd.com/skills/ruchernchong/update-issue
7 model: sonnet
8---
9
10## Language Conventions
11
12**Infer language style from the project:**
13- Analyze existing issues, documentation, and commit messages to detect the project's language variant (US English, UK English, etc.)
14- Match the spelling conventions found in the project (e.g., "initialize" vs "initialise", "behavior" vs "behaviour")
15- Maintain consistency with the project's established language style throughout issue updates
16
17---
18
19Update a GitHub issue with the following workflow:
20
211. Check if we're in a GitHub repository
222. **Identify the issue to update:**
23 - If issue number is provided (e.g., "issue 123", "#456", or "789"), use that issue
24 - If not provided, ask the user for the issue number
253. **View current issue details:**
26 - Use `gh issue view` to display current state
27 - Show title, body, labels, assignees, and state
28 - This helps understand what needs updating
294. **Check for ISSUE_TEMPLATE format:**
30 - Look for issue templates in `.github/ISSUE_TEMPLATE/` or `.github/` directories
31 - If the current issue follows a template, identify which template
32 - Parse template structure to preserve required sections
335. **Determine what to update:**
34 - Ask what fields the user wants to update (title, body, labels, assignees, state)
35 - Accept input for new values
36 - If updating body and template exists, maintain template structure
376. **Apply updates with validation:**
38 - For title: Use natural, descriptive language
39 - For body with template: Preserve template sections and formatting
40 - For body without template: Use clear, structured format
41 - For labels: Only use existing repository labels
42 - For assignees: Only assign valid repository collaborators
43 - Use `gh issue edit` to apply changes
447. **Confirm and display results:**
45 - Show summary of all updates made
46 - Display success message with link to updated issue
47
48For the issue title:
49- Use natural, descriptive language
50- Keep it concise but informative
51- Match the style of existing issue titles in the repository
52
53For the issue body (when using ISSUE_TEMPLATE format):
54- Follow the exact template structure
55- Preserve required sections and formatting
56- Update only the sections being changed
57- Maintain template sections
58
59For the issue body (custom format):
60- Include clear problem statement or feature details
61- Add relevant context from the update
62- Keep it structured and actionable
63- Maintain existing formatting style when possible
64
65For labels and assignees:
66- Only add labels that already exist in the repository
67- Validate assignees are valid repository collaborators
68- Show current labels and assignees before making changes