itx-bug-update
Skill67 starsChanged 2 months agoApache-2.0View on GitHub
Add a comment to an existing bug issue
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- clawctl-lmworkSkill
- clawctlSkill
- clawctl-uatSkill
- create-playwrightSkill
- create-vhsSkill
- itx-bug-newSkill
- itx-executeSkill
- itx-issue-newSkill
- itx-issue-updateSkill
- itx-noteSkill
- itx-plan-createSkill
- itx-plan-scaffoldSkill
- itx-pr-statusSkill
- itx-releaseSkill
- itx-review-prSkill
- itx-triageSkill
- itx-verifySkill
- sync-upstreamSkill
- tddSkill
- blog-authorSkill
- daily-digestSkill
- docs-syncSkill
- issue-triageSkill
- release-watcherSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Add a comment to an existing GitHub bug issue.
- Very specific: line 17
Validate Issue: Verify the issue exists and has bug label
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bug Update
Add a comment to an existing GitHub bug issue.
Instructions
- Parse Arguments: Extract issue number and comment text from arguments
- First argument: issue number (required)
- Remaining text: comment content (required)
- Validate Issue: Verify the issue exists and has
buglabelgh issue view <number> --json number,title,labels - Add Comment: Post the comment with prompt log
gh issue comment <number> --body "<comment with prompt log>" Comment Format:
<comment text> --- <details> <summary>Prompt Log</summary> **Stage**: bug-update **Skill**: /itx-bug-update **Timestamp**: <ISO timestamp> **Model**: <model> ```prompt <original user prompt that triggered this update></details> ```- Return: Confirmation with issue URL
Examples
/itx-bug-update 42 Added debug logging, the error occurs in registry.py line 156Notes
- Warn if the issue doesn't have a
buglabel (may be wrong issue type) - Include relevant technical details from the conversation
Prompt Logging
REQUIRED: Append prompt log to .itx/<N>/00_PLAN.md.
See AGENTS.md for format specification.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

