code-notify
Use when a task should trigger a local completion notification through code-notify, or when configuring cross-tool notification behavior for Codex, Cursor, Claude, Gemini, or similar agent workflows. Verify the installed command or existing local integration before relying on it.
- License 许可
- Unlicense
- 所属仓库
- saski/arnesto
- 最近更新
- 2026-11-12
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- code-notify
- description
- Use when a task should trigger a local completion notification through code-notify, or when configuring cross-tool notification behavior for Codex, Cursor, Claude, Gemini, or similar agent workflows. Verify the installed command or existing local integration before relying on it.
03 SKILL.md 正文
Code Notify
Goal
Make supported AI tools finish noisy terminal work with a local notification instead of requiring manual polling.
Use This Skill When
- The user asks to enable or wire completion notifications for an AI coding tool.
- A workflow should notify when a long-running task finishes or needs attention.
- You are documenting shared agent capabilities in a cross-tool setup.
Cross-Platform Rules
- Treat
code-notifyas an optional local dependency managed outside this repository. - Verify the installed command, wrapper, hook, or config before using it.
- Prefer shared wording and forward-slash paths so the guidance works across macOS, Linux, and Windows-compatible shells.
- Keep the integration additive. Do not replace existing hooks or notification settings unless the user asks.
Workflow
- Detect whether the current tool already has a notification hook or wrapper configured.
- Look for a local
code-notifycommand, alias, script, or documented install path before assuming invocation details. - If present, use it for end-of-task or attention-needed notifications only.
- If missing, tell the user the integration is unavailable in the current shell and continue without blocking the main task.
Output Guidance
- Mention that
code-notifyis available only after verifying the local installation. - Keep notification instructions tool-agnostic unless the user asks for a specific platform.
- Prefer concise setup notes over tool-specific prose duplication.
04 同仓库更多 Skills
visualize
Use /visualize for creating compact charts, diagrams, or other visuals inline as part of the conversation itself. It chooses among Markdown tables, Mermaid, inline HTML, and other supported in-transcript forms. Use Canvas for durable artifacts outside the transcript that users may revisit, refine, or share.
update-cursor-settings
Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
update-cli-config
View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.
statusline
Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.
split-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
shell
Runs the rest of a /shell request as a literal shell command. Use only when the user explicitly invokes /shell and wants the following text executed directly in the terminal.