Debug Os Failure On GitHub
strands-agents/box
Debug a CI failure on an OS you are not on (you are on Linux, it fails on macos-latest, or the reverse) without opening a pull request per attempt.
File a Neru bug report or feature request that matches the repo's issue forms: duplicate check first, every required field filled with real diagnostics, correct labels.
Install Neru File Issue
$ npx skills add y3owk1n/neru --skill neru-file-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install y3owk1n/neru neru-file-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/y3owk1n/neru.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/neru-file-issue .claude/skills/neru-file-issue && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "neru-file-issue" agent skill from https://github.com/y3owk1n/neru/tree/main/.agents/skills/neru-file-issue into .claude/skills/neru-file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neru-file-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/y3owk1n/neru/tree/main/.agents/skills/neru-file-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add y3owk1n/neru --skill neru-file-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install y3owk1n/neru neru-file-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/y3owk1n/neru.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/neru-file-issue .agents/skills/neru-file-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "neru-file-issue" agent skill from https://github.com/y3owk1n/neru/tree/main/.agents/skills/neru-file-issue into .agents/skills/neru-file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neru-file-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add y3owk1n/neru --skill neru-file-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install y3owk1n/neru neru-file-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/y3owk1n/neru.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/neru-file-issue .cursor/skills/neru-file-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "neru-file-issue" agent skill from https://github.com/y3owk1n/neru/tree/main/.agents/skills/neru-file-issue into .cursor/skills/neru-file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neru-file-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/y3owk1n/neru.git --path .agents/skills/neru-file-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add y3owk1n/neru --skill neru-file-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install y3owk1n/neru neru-file-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/y3owk1n/neru.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/neru-file-issue .gemini/skills/neru-file-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "neru-file-issue" agent skill from https://github.com/y3owk1n/neru/tree/main/.agents/skills/neru-file-issue into .gemini/skills/neru-file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neru-file-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install y3owk1n/neru neru-file-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add y3owk1n/neru --skill neru-file-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/y3owk1n/neru.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/neru-file-issue .github/skills/neru-file-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "neru-file-issue" agent skill from https://github.com/y3owk1n/neru/tree/main/.agents/skills/neru-file-issue into .github/skills/neru-file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neru-file-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add y3owk1n/neru --skill neru-file-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install y3owk1n/neru neru-file-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/y3owk1n/neru.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/neru-file-issue .opencode/skills/neru-file-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "neru-file-issue" agent skill from https://github.com/y3owk1n/neru/tree/main/.agents/skills/neru-file-issue into .opencode/skills/neru-file-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neru-file-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
neru-file-issue- GitHub stars
- 802
- Token cost
- ~890 tokens
- SKILL.md length
- 419 words
- Files
- 2
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
File a Neru bug report or feature request that matches the repo's issue forms: duplicate check first, every required field filled with real diagnostics, correct labels.
- Works in 2 steps: Search for duplicates — the forms make… → Route non-issues away. Questions and…
- Draft a GitHub issue for Neru
- SKILL.md covers Always, before filing, Bug report (--label bug), Feature request (--label… and Filing
- Calls gh
What it does
Neru File Issue is an agent skill from y3owk1n/neru. File a Neru bug report or feature request that matches the repo's issue forms: duplicate check first, every required field filled with real diagnostics, correct labels. Use when asked to open, file, or draft a GitHub issue for Neru. Not for pull requests.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Testing & QA, covering QA and bug reports and Pull requests. It works with GitHub, Linux and macOS. The repository describes itself as: Hints, grids and vim keys for your whole desktop. Built for macOS, linux and windows, natively. The licence is MIT.
When your agent uses it
- Draft a GitHub issue for Neru
- Tasks that involve QA and bug reports
- Tasks that involve Pull requests
Example prompts
- “/neru-file-issue”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Search for duplicates — the forms make humans attest to this, so do it
- Route non-issues away. Questions and config help belong in
What it can do on your machine
Read from SKILL.md and the folder at commit 592240e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Neru File Issue loads about 890 tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 419 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from y3owk1n/neru at commit 592240e, republished under its MIT licence (© y3owk1n). 419 words, ~890 tokens.
Download SKILL.mdSave it as
.claude/skills/neru-file-issue/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- neru-file-issue
- description
- File a Neru bug report or feature request that matches the repo's issue forms: duplicate check first, every required field filled with real diagnostics, correct labels. Use when asked to open, file, or draft a GitHub issue for Neru. Not for pull requests.
Filing an issue in Neru
Blank issues are disabled (.github/ISSUE_TEMPLATE/config.yml) — everything
goes through a form, and an agent-filed issue must contain the same fields the
form enforces. gh issue create bypasses form validation, so you are the
validator.
Always, before filing
- Search for duplicates — the forms make humans attest to this, so do it
for real:
gh issue list --search "<keywords>" --state all, plus discussions for feature ideas. Found one? Comment there instead of filing. - Route non-issues away. Questions and config help belong in
Discussions; Linux porting talk belongs in discussion #559; "is this
supported yet" is answered by the Platform Support matrix in the README
and
docs/reference/platform-support.md. Filing an issue for these is wrong even if the user asked for an issue — say so and offer the right venue.
Bug report (--label bug)
Mirror bug_report.yml's fields as markdown sections, all of them:
- Neru version — real output of
neru --version, never guessed. - Operating system and OS version (
sw_verson macOS; distro + compositor on Linux, since behavior differs across X11/wlroots/KDE/GNOME). - Navigation mode — hints / grid / recursive grid / scroll / n.a.
- What happened / What did you expect — observed vs expected, concrete.
- Steps to reproduce — numbered, from
neru launch, minimal. - Config (relevant sections) — only the TOML sections involved, fenced as
toml. Strip anything personal (macro contents, exec commands). - Screenshots / recordings and Additional context when they help;
neru doctoroutput is gold for capability/permission-shaped bugs.
Linux/Windows caveat from the form: many features are intentionally
unimplemented there. If neru doctor reports the capability as stub, it is
a roadmap item, not a bug — check the matrix before filing.
Show full SKILL.md (156 more words)Show less
Feature request (--label enhancement)
Mirror feature_request.yml:
- Category — one of: Navigation, Mouse actions, Configuration, CLI / IPC, UI / Overlays, Performance, Platform support (Linux / Windows), Other.
- Target platform — All platforms / macOS / Linux / Windows.
- Problem or use case — the need, not the mechanism. This is the section maintainers judge; write it first and best.
- Proposed solution, Alternatives considered, optional Screenshots / mockups.
- Contribution — state plainly whether a PR will follow.
Filing
Draft the body, show it to the user before creating (an issue posts publicly under their account), then:
gh issue create --title "<concise, user-facing summary>" --label bug --body-file <draft>Title style matches the tracker: plain sentence, no conventional-commit prefix, no trailing period.
The forms apply bug / enhancement automatically; gh does not, so pass it
yourself — and add the axes the forms never cover: platform: macOS /
platform: linux / platform: windows or cross-platform, the matching
area: * (overlays, event-tap, hotkeys, accessibility, cli,
config, domain, ipc, ui, infra), and stub implementation when the
ask is replacing a CodeNotSupported stub. gh label list is the authority.
© y3owk1n, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/neru-file-issue of y3owk1n/neru.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 592240e
Compare with similar skills
Neru File Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Neru File Issue this skilly3owk1n/neru | 802 | — | ~890 | Automated safety check: Pass | MIT | |
| Debug Os Failure On GitHubstrands-agents/box | 299 | — | ~1.3k | Automated safety check: Notes | Apache-2.0 | |
| cmux Screenshot and Recordingmanaflow-ai/cmux | 28k | — | ~992 | Automated safety check: Pass | Custom licence | |
| Ax RepoNecmttn/ax | 115 | — | ~1.8k | Automated safety check: Pass | AGPL-3.0 | |
| Dev CompleteFHIR/fhir-codegen | 155 | — | ~9.6k | Automated safety check: Pass | MIT | |
| Termio Bug Reporttermio-sh/termio | 539 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
cmux Screenshot and Recording
manaflow-ai/cmux
Captures PNG or JPEG screenshots and MP4 or GIF clips of cmux windows from the command line, as visual evidence for pull requests and bug reports.
Ax Repo
Necmttn/ax
Star the ax repo, file an issue / bug report, or fork-and-open-a-PR against github.com/Necmttn/ax on the user's behalf, by shelling out to the gh CLI.
Dev Complete
FHIR/fhir-codegen
Drives the entire local inner loop in one invocation, as a conductor over the skills that own each role.
Termio Bug Report
termio-sh/termio
Diagnose a termio hang, beachball, crash, or 'it froze again' from the evidence macOS and termio actually leave behind — live process samples, crash and CPU-burn reports, the unified log, the…
Community Triage
roryeckel/wyoming_openai
GitHub issues, pull requests, bug reports, scope questions, and support threads.
More from y3owk1n/neru
Neru Add CLI Command
y3owk1n/neru
Add a Neru CLI command or flag: cobra command in internal/cli, IPC handler in internal/app/ipcctrl, service/mode work behind it, man pages, and docs/reference/cli.md.
Neru Add Config Option
y3owk1n/neru
Add or change a Neru config.toml option end to end: struct field, shared and platform defaults, validation, examples, docs, and hot-reload behavior.
Neru Add Platform Feature
y3owk1n/neru
Implement or stub Neru functionality for a specific OS/backend: port contract, build-tagged file slots, factory wiring, CodeNotSupported stubs, capability matrix, contract tests, and the docs…
Neru Ask
y3owk1n/neru
Answer a Neru user's question about what Neru does, which command, flag, or config key does a thing, why something does not work, or what to try next, from the help, man pages, and docs of their…
Neru Create PR
y3owk1n/neru
Commit working changes and open a Neru pull request the maintainer's way: conventional commit subjects, a PR title written for the changelog, the just ci gate, and the repo PR template filled…
Neru Setup Config
y3owk1n/neru
Set up or change a user's Neru config.toml: find or create the file, bind or disable hotkeys, tune hints, grids, or scroll, add per-app overrides, macros, or declared modes, set up the login…
Related
Categories
Questions about Neru File Issue
What does Neru File Issue do?
File a Neru bug report or feature request that matches the repo's issue forms: duplicate check first, every required field filled with real diagnostics, correct labels. Neru File Issue is an agent skill from y3owk1n/neru. File a Neru bug report or feature request that matches the repo's issue forms: duplicate check first, every required field filled with real diagnostics, correct labels.
When should I use Neru File Issue?
Neru File Issue fits situations like: draft a GitHub issue for Neru; tasks that involve QA and bug reports; tasks that involve Pull requests.
How do I install Neru File Issue in Claude Code?
Run `npx skills add y3owk1n/neru --skill neru-file-issue -a claude-code`. Or copy the skill folder (.agents/skills/neru-file-issue in y3owk1n/neru) into .claude/skills/neru-file-issue in your project. Claude Code loads it when a task matches its description.
How do I install Neru File Issue in Codex?
Run `npx skills add y3owk1n/neru --skill neru-file-issue -a codex`. Or copy the skill folder (.agents/skills/neru-file-issue in y3owk1n/neru) into .agents/skills/neru-file-issue in your project. Codex loads it when a task matches its description.
Can I use Neru File Issue in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add y3owk1n/neru --skill neru-file-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/neru-file-issue, .gemini/skills/neru-file-issue, .github/skills/neru-file-issue and .opencode/skills/neru-file-issue in your project.
What does Neru File Issue need to run?
Going by SKILL.md and its folder, Neru File Issue needs the command-line tools its instructions call (gh).
Does Neru File Issue access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Neru File Issue safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Neru File Issue use?
Neru File Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Neru File Issue use?
About 890 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Neru File Issue?
Skills that share tags, products or a category with Neru File Issue: Debug Os Failure On GitHub (strands-agents/box, 299 stars), cmux Screenshot and Recording (manaflow-ai/cmux, 28k stars), Ax Repo (Necmttn/ax, 115 stars) and Dev Complete (FHIR/fhir-codegen, 155 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Neru File Issue?
y3owk1n (a GitHub user) maintains it in y3owk1n/neru, which has 802 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 10, 2026.
Source: y3owk1n/neru on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.