iwe-bug-report
Skill0 starsChanged 26 days agoMITView on GitHub
Report a bug or platform issue in IWE. Creates a GitHub issue in IWE.
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- TserenTserenov/FMT-exocortex-templatetheir own version, first seen Nov 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- TserenTserenov/FMT-exocortex-template★ 64same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-faultSkill
- apply-capturesSkill
- archgateSkill
- artifactorSkill
- audit-docsSkill
- audit-installationSkill
- author-modeSkill
- bottleneck-pickSkill
- check-secretSkill
- consentSkill
- day-closeSkill
- day-openSkill
- decomposeSkill
- diagnoseSkill
- discovery-sessionSkill
- extendSkill
- fpfSkill
- integration-gateSkill
- iwe-platform-redteamSkill
- iwe-restoreSkill
- iwe-rules-reviewSkill
- iwe-updateSkill
- keSkill
- kimi-peer-writerSkill
- local-llmSkill
- month-closeSkill
- org-devSkill
- pack-creatorSkill
- pack-newSkill
- peer-conversationSkill
- personal-guide-renderSkill
- personal-guide-startSkill
- platform-bottleneckSkill
- repo-newSkill
- restore-exocortexSkill
- run-protocolSkill
- setup-wakatimeSkill
- skill-creatorSkill
- strategy-sessionSkill
- skill-idSkill
- thinkSkill
- transcribeSkill
- vdvSkill
- verify-hypothesesSkill
- verifySkill
- week-close-pilotSkill
- week-closeSkill
- wp-newSkill
- w-reflectionSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Very specific: line 37
If $ARGUMENTS is empty, missing, or equals --help/-h/help — do NOT create an issue.
- Distinctive: line 62
If any element is not specified, omit the corresponding section from the issue (do not leave empty headings).
- Very specific: line 78
If gh is not authorized or not installed, output:
- Distinctive: line 91
Verify the label before use:
- Distinctive: line 97
Run (substituting real values):
- Very specific: line 130
If gh returned an error, output the full error text.
≈ “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
IWE Platform Bug Report
Issue: $ARGUMENTS
When to use
Report a bug or platform issue in IWE. Creates a GitHub issue in IWE.
Algorithm
Step 0. Check for a help request (issue #274)
If $ARGUMENTS is empty, missing, or equals --help/-h/help — do NOT create an issue. Instead, output:
"
/iwe-bug-report [issue description]— reports an IWE platform bug and creates a GitHub issue in IWE. Describe what happened and what was expected, for example:/iwe-bug-report day-close does not archive DayPlan."
Stop execution.
Step 1. Categorization
Determine the category based on the content of $ARGUMENTS:
| Label | When |
bug | A Skill / Protocol / Script does not behave as intended |
documentation | An inaccuracy or gap in documentation / memory / SKILL.md |
enhancement | Improvement to existing behavior (not new functionality) |
question | Behavior is unclear; clarification is needed |
Step 2. Collect details
Extract from $ARGUMENTS and the Session context:
- What happened: the specific observable behavior
- What was expected: the correct behavior per the Protocol
- Steps to reproduce: command / Skill / trigger (if applicable)
- Location: path to the Skill / Protocol / Script or file name
If any element is not specified, omit the corresponding section from the issue (do not leave empty headings).
Step 3. Get the IWE version
Run:
git -C "${IWE_WORKSPACE:-$HOME/IWE}/IWE" log -1 --format="%h %ad" --date=short 2>/dev/null || echo "unknown"Step 4. Verify the gh CLI
Run:
gh auth status 2>&1 | head -3If gh is not authorized or not installed, output:
"
ghCLI not found or not authorized. Install it (macOS:brew install gh; Linux:apt install ghor https://cli.github.com/), then rungh auth login. Issue not created." Stop execution.
Step 5. Create the issue
Assemble the variables:
TITLE: up to 80 characters, format[TYPE] Brief descriptionCATEGORY: label from Step 1DATE: today's date (YYYY-MM-DD)IWE_VERSION: from Step 3
The labels in iwesys/IWE are a copy of an external Repository and may diverge from the table in Step 1 (issue #457: docs was renamed to documentation; in that case gh issue create --label fails and the issue is not created at all).
Verify the label before use:
gh label list --repo iwesys/IWE --json name -q '.[].name' | grep -qx "CATEGORY"Label found → use --label "CATEGORY" below as normal. Label not found → create the issue WITHOUT the --label flag (do not block creation due to label mismatch) and append the following line to the end of ## Context: - Label not created: "CATEGORY" not found in the Repository (check the current list via gh label list).
Run (substituting real values):
gh issue create \
--repo iwesys/IWE \
--title "TITLE" \
--label "CATEGORY" \
--body "$(cat <<'BODY'
## What happened
[description]
## What was expected
[expected behavior]
## Steps to reproduce
[steps or "not applicable"]
## Context
- File / Skill: [path or name]
- Date: DATE
- IWE commit: IWE_VERSION
BODY
)"Step 6. Report
Output a single line:
"Issue created: [URL]"
If gh returned an error, output the full error text.
<!-- USER-SPACE --><!-- /USER-SPACE -->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.

