notify

Estrelas7

Forks2

Atualizado18 de julho de 2026 às 14:58

On-demand AFK Telegram bridge: send completion/blocker pings and receive replies via a background listener that wakes the session. OFF by default. Use on /notify, going AFK, or steering from Telegram.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

trevormil

trevormil/TerMinal

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	notify
description	On-demand AFK Telegram bridge: send completion/blocker pings and receive replies via a background listener that wakes the session. OFF by default. Use on /notify, going AFK, or steering from Telegram.

/notify — On-demand AFK Telegram bridge

A two-way bridge between an AFK user and this session via the user's personal Telegram bot. Off by default — arm it only when the user signals AFK ("I'm AFK", "ping me when done", "steer from Telegram", "going for a walk").

Prerequisite (machine-level, set up once)

The send/receive scripts and credentials live in the user's home, not the repo (they're personal + secret, so they can't be committed):

~/.claude/bin/telegram-notify.sh — send a message
~/.claude/bin/telegram-poll.sh — fetch new messages (offset-tracked)
~/.claude/bin/tg-listener.sh — foreground listener loop (receive)
~/.claude/.telegram-notify.json — bot_token + chat_id (mode 600)

If these don't exist on the machine, the bridge can't run — tell the user and stop (this template can't provision personal Telegram creds). When they exist, this skill just operationalizes them for the current repo/session.

Arming (when the user goes AFK)

Immediately launch the listener via Bash(run_in_background=true):
```
Bash(command="~/.claude/bin/tg-listener.sh", run_in_background=true)
```
The loop polls Telegram and exits the moment a message arrives — that exit wakes the session. Double-arming is safe (it self-prunes prior instances).
Send a one-line ack: ~/.claude/bin/telegram-notify.sh --kind=info "On it — armed for AFK."
Work autonomously. When the listener fires, ingest the message and respond.
Re-arm a fresh listener at the end of every turn while AFK — that's what keeps the bridge continuously connected.
Disarm when the user says "I'm back" / "AFK off" / "stop pinging": stop re-arming.

When to send (send side is event-driven, not per-turn)

Major checkpoints: work kickoff, a PR opened, a phase done, the whole task done.
A true blocker needing a human decision (--kind=blocked / --kind=question), with the question + 2-3 options.
/notify <message> — send verbatim (--kind=info unless a kind is passed).
Heartbeat: if a single task runs >5 min with no ping, send a one-line --kind=info so the user knows it's alive.

Don't ping per shell command, for routine completions, or for things the user is watching on screen.

Message kinds

--kind=done (✅) · --kind=blocked (⛔) · --kind=question (❓) · --kind=info (ℹ️) · none (plain). Phone-readable: 1–4 lines, lead with the outcome, include URLs/paths, plain text (no markdown). Never send secrets.

~/.claude/bin/telegram-notify.sh --kind=done "PR #42 opened, tests green. Review running in background."
~/.claude/bin/telegram-notify.sh --kind=blocked "Migration needs prod creds. Skip backfill and ship, or wait?"

Relationship to autonomous modes

/stacked-mr (autonomous overnight stacking) runs AFK by default and uses this bridge for its checkpoint pings. When the user kicks off /stacked-mr, arm the listener as part of starting it.

Mais deste repositório

mesmo repositório

code-review

trevormil/TerMinal

Compatibility launcher for the code-review agent. Delegates a GitHub/GitLab PR review to Codex: deterministic preflight does recon, then Codex scores six axes into one artifact at .TerMinal/reviews/<pr>/<sha>.md (v2) or .reviews/<pr>/<sha>.md (legacy v1). Use on /code-review or 'review this PR'.

2026-07-187

digest

trevormil/TerMinal

Human-review digest for a PR/MR — chunks the diff into a noise-filtered, risk-ranked, code-first review surface (green/red diffs, 🟢/🟡/🔴, design-decision callouts) WITHOUT abstracting the code away. Deterministic chunker + one bounded codex pass. Sits alongside /code-review (the gate) and /iterate (tests). Use on /digest or 'digest this PR for review'. Renders in TerMinal.

2026-07-187

document-audit

trevormil/TerMinal

Audit docs/ and ~/.claude/docs/ for rot — broken refs, stale runbooks, ADR contradictions, architecture drift, orphan CLAUDE.md. Reports only; never auto-edits. Use on /document-audit or 'check doc health'.

2026-07-187

document

trevormil/TerMinal

Sweep recent changes and propose doc updates (ADRs, runbooks, learnings, architecture, per-folder CLAUDE.md), one candidate at a time. Use on /document, 'capture decisions', or natural post-commit/post-PR pauses.

2026-07-187

emergency-fix

trevormil/TerMinal

FORCE-MODE hotfix: smallest patch → commit → push DIRECTLY to main → follow-up ticket. Needs TERMINAL_FORCE_MAIN=1 (hook-enforced). Use on /emergency-fix or 'this is breaking prod' / 'hotfix' / 'we need to revert now'.

2026-07-187

enqueue-request

trevormil/TerMinal

Enqueue a one-off TerMinal automation-inbox request (can create Activity, tickets, HITL, agent runs, or background tasks). Use on /enqueue-request or to queue a durable local automation request.

2026-07-187

/notify — On-demand AFK Telegram bridge

Prerequisite (machine-level, set up once)

The send/receive scripts and credentials live in the user's home, not the repo (they're personal + secret, so they can't be committed):

~/.claude/bin/telegram-notify.sh — send a message

~/.claude/bin/telegram-poll.sh — fetch new messages (offset-tracked)

~/.claude/bin/tg-listener.sh — foreground listener loop (receive)

~/.claude/.telegram-notify.json — bot_token + chat_id (mode 600)

Arming (when the user goes AFK)

Immediately launch the listener via Bash(run_in_background=true):

Bash(command="~/.claude/bin/tg-listener.sh", run_in_background=true)

The loop polls Telegram and exits the moment a message arrives — that exit wakes the session. Double-arming is safe (it self-prunes prior instances).

Send a one-line ack: ~/.claude/bin/telegram-notify.sh --kind=info "On it — armed for AFK."

Work autonomously. When the listener fires, ingest the message and respond.

Re-arm a fresh listener at the end of every turn while AFK — that's what keeps the bridge continuously connected.

Disarm when the user says "I'm back" / "AFK off" / "stop pinging": stop re-arming.

When to send (send side is event-driven, not per-turn)

Major checkpoints: work kickoff, a PR opened, a phase done, the whole task done.

A true blocker needing a human decision (--kind=blocked / --kind=question), with the question + 2-3 options.

/notify <message> — send verbatim (--kind=info unless a kind is passed).

Heartbeat: if a single task runs >5 min with no ping, send a one-line --kind=info so the user knows it's alive.

Don't ping per shell command, for routine completions, or for things the user is watching on screen.

Message kinds

~/.claude/bin/telegram-notify.sh --kind=done "PR #42 opened, tests green. Review running in background." ~/.claude/bin/telegram-notify.sh --kind=blocked "Migration needs prod creds. Skip backfill and ship, or wait?"

Relationship to autonomous modes

/stacked-mr (autonomous overnight stacking) runs AFK by default and uses this bridge for its checkpoint pings. When the user kicks off /stacked-mr, arm the listener as part of starting it.