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.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Blank issues are disabled (.github/ISSUE_TEMPLATE/config.yml), so 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.
gh issue list --search "<keywords>" --state all, plus
discussions for feature ideas. Found one? Comment there instead of filing.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.--label bug)Mirror bug_report.yml's fields as markdown sections, all of them:
neru --version, never guessed.sw_vers on macOS, distro and
compositor on Linux, since behavior differs across X11/wlroots/KDE/GNOME).neru launch, minimal.toml. Strip anything personal (macro contents, exec commands).neru doctor output is the most useful evidence 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.
--label enhancement)Mirror feature_request.yml:
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.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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. Use when adding or changing user-facing commands, subcommands, or flags. Not for config.toml options.
日本語の概要は準備中です。原文の説明を表示しています。
Add or change a Neru config.toml option end to end: struct field, shared and platform defaults, validation, examples, docs, and hot-reload behavior. Use whenever a change adds, renames, or removes a key in the TOML config schema. Not for theme palette entries or CLI flags.
日本語の概要は準備中です。原文の説明を表示しています。
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 ownership table. Use for any change under internal/adapter/platform or any *_darwin/_linux/_windows file. Not for pure-Go domain logic.
日本語の概要は準備中です。原文の説明を表示しています。
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 installed version rather than from memory. Routes config work to neru-setup-config. Use when a Neru user asks what Neru can do, how to do something with it, which command to run, why hints or a hotkey do nothing, or which skill to use.
日本語の概要は準備中です。原文の説明を表示しています。
Help a Neru user build a tool on top of Neru, such as a status bar, a launcher, voice control, a companion UI, automation from another hotkey tool, a Go program, or a client for the IPC socket in another language. Picks the interface, checks the installed version has it, reads the contract from that version's docs, and runs the result against the live daemon. Routes config and hooks work to neru-setup-config. Use when a Neru user wants to script Neru, read its state, follow its events, drive it from another program, or write code against its CLI, socket, or Go client.
日本語の概要は準備中です。原文の説明を表示しています。
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 honestly. Use when asked to commit, create a PR, open a pull request, or ship finished work in this repo.
日本語の概要は準備中です。原文の説明を表示しています。