itx-bug-new
Skill67 starsChanged 2 months agoApache-2.0View on GitHub
Create a GitHub bug report from current context
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-updateSkill
- 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
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Create a GitHub issue for a bug based on the current conversation context.
- Distinctive: line 19
Ask for Customer Outcome: Use the harness's user-question facility to ask:
- Distinctive: line 27
Form Issue Title: Use the customer outcome as the issue title.
- Distinctive: line 33
If the user provided a description argument, use it for context
- Very specific: line 52
Create Issue: Use gh issue create with:
- Distinctive: line 105
Always ask for customer outcome before creating the issue
- Very specific: line 107
Always add needs-triage label for new bugs
- Distinctive: line 109
If steps to reproduce are unclear, note that in the issue
- Very specific: line 114
REQUIRED: After creating the issue, append prompt log to .itx/<N>/00_PLAN.md.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 Report Creation
Create a GitHub issue for a bug based on the current conversation context.
Instructions
- Analyze Context: Review the current conversation for:
- Error messages and stack traces
- Unexpected behavior descriptions
- Steps that led to the issue
- Environment details (version, OS, etc.)
Ask for Customer Outcome: Use the harness's user-question facility to ask:
"What should the user be able to do when this bug is fixed?"
Example outcomes:
- "User can install dependencies without version mismatch errors"
- "User can add resources with special characters in names"
- "User can run status command without timeout"
- Form Issue Title: Use the customer outcome as the issue title.
- Format:
<outcome>(what the user can do after fix) - Example: "User can install dependencies without version mismatch errors"
- The user can change this later if needed
- Format:
- Gather Details:
- If the user provided a description argument, use it for context
- Identify steps to reproduce if available
- Note environment details
- Load Project Name (for environment section):
ITX_CONFIG="$(git rev-parse --show-toplevel)/.claude/itx-config.json" if [ -f "$ITX_CONFIG" ]; then PROJECT_NAME=$(jq -r '.project.name // ""' "$ITX_CONFIG") VERSION_LABEL=$(jq -r '.project.version_label // "Version"' "$ITX_CONFIG") fi # Fallback: use repository name if no config if [ -z "$PROJECT_NAME" ]; then REMOTE_URL=$(git config --get remote.origin.url) PROJECT_NAME=$(echo "$REMOTE_URL" | sed -E 's/.*[:/]([^/]+\/[^/]+)(\.git)?$/\1/' | cut -d'/' -f2) fi - Create Issue: Use
gh issue createwith:gh issue create \ --title "<customer outcome from step 3>" \ --label "bug" \ --label "needs-triage" \ --body "<structured bug report>" Bug Report Body Format:
## Customer Outcome <The outcome statement - what user can do when fixed> ## Description <What is currently happening / the bug> ## Steps to Reproduce 1. <step> 2. <step> ## Expected Behavior <What should happen> ## Actual Behavior <What actually happens> ## Environment - <project name> version: <version> - Platform: <os/platform> - Other relevant details: <details> --- <details> <summary>Prompt Log</summary> **Stage**: bug-creation **Skill**: /itx-bug-new **Timestamp**: <ISO timestamp> **Model**: <model> ```prompt <original user prompt/context that led to this bug></details> ```- Return: The issue URL and number
Notes
- Always ask for customer outcome before creating the issue
- The outcome becomes the title - focus on what the user gains
- Always add
needs-triagelabel for new bugs - Include as much context as available from the conversation
- If steps to reproduce are unclear, note that in the issue
- Project name dynamically detected or loaded from config
Prompt Logging
REQUIRED: After creating the issue, append prompt log to .itx/<N>/00_PLAN.md.
See AGENTS.md for format specification.
mkdir -p .itx/<issue-number>
# Append prompt log to .itx/<issue-number>/00_PLAN.mdDoes 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.

