원클릭으로
regular-ping
// Set up, inspect, retarget, pause, or resume recurring tmux pings ("regular pings") using `t jobs`. Use when the user asks to create a scheduled ping for a session, check existing pings, or move a ping to another tmux session.
// Set up, inspect, retarget, pause, or resume recurring tmux pings ("regular pings") using `t jobs`. Use when the user asks to create a scheduled ping for a session, check existing pings, or move a ping to another tmux session.
Fetch and transcribe Google Recorder voice notes. Use when the user shares a recorder.google.com link and wants the original audio file, a transcript, or wants to act on a voice note.
Initialize a new Python library with modern tooling, packaging, tests, and optional CLI support. Use when the user wants to scaffold a new Python package.
Add the standardized CI publish workflow (`.github/workflows/publish.yml` + `make release`) to an existing Python project so PyPI releases happen on tag push. Use when a project still publishes via a local script (`publish.py`, `hatch publish`, `twine upload`) or has no automated publish at all.
Release the current project to its package registry and GitHub by bumping the version, pushing a tag, and letting CI publish. Works for any project (Python/PyPI, Rust/crates.io, Node/npm, etc.) that has a CI publish workflow keyed off `v*` tags.
Run and fix stylint checks for prose, Markdown, lessons, workshops, docs, and agent-written text. Use when editing written content or when the user asks for style, polish, or lint cleanup.
Transcribe local audio files with the OpenAI Audio Transcriptions API without adding OpenAI dependencies to the target project.
| name | regular-ping |
| description | Set up, inspect, retarget, pause, or resume recurring tmux pings ("regular pings") using `t jobs`. Use when the user asks to create a scheduled ping for a session, check existing pings, or move a ping to another tmux session. |
| allowed-tools | Bash(t *), Bash(tmux *) |
In this environment, a "regular ping" means a recurring ping managed through t jobs.
If the user only knows the recent-session ID, resolve it first:
t
t list
If the agent is already inside the target tmux session, :current is valid for job commands:
t jobs add :current --every 20m --message "..."
t jobs edit <job-id> --session :current
If multiple similar sessions exist, inspect them before attaching the ping to the wrong one:
tmux list-panes -t <session> -F '#{session_name}:#{window_index}.#{pane_index}:#{pane_current_command}:#{pane_title}:#{pane_active}'
Always prefer the exact tmux session name over a guessed prefix.
List all jobs:
t j
List jobs for one session:
t jobs list --session <session>
Inspect one job:
t jobs show <job-id>
Check recent delivery logs:
t jobs logs --limit 20
Notes:
t j is shorthand for t jobst jobs editFor a short inline prompt:
t jobs add <session> --every 20m --message "Continue until all issues are resolved."
For a longer prompt:
t jobs add <session> --every 20m --message-file prompts/<name>.txt
After creating the job, verify it:
t jobs list --session <session>
t jobs show <job-id>
If the user wants an immediate one-off message right now, send it separately:
t send <session> --message "..."
Retarget a job to the correct session:
t jobs edit <job-id> --session <session>
Change interval or prompt:
t jobs edit <job-id> --every 30m
t jobs edit <job-id> --message "..."
Pause or resume one job:
t jobs pause <job-id>
t jobs resume <job-id>
Pause or resume all jobs for the current tmux session:
t jobs pause-current
t jobs resume-current
Remove a job that is no longer needed:
t jobs remove <job-id>
t jobs show <job-id> after changes.t send.