amit-operator-commands

Routes short operator command phrases into safe worker, git, and cleanup workflows.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/amitkarpe/agent-skills --skill amit-operator-commands-amitkarpe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: amit-operator-commands
Source: https://github.com/amitkarpe/agent-skills/tree/main/skills/amit-operator-commands
Command: npx skills add https://github.com/amitkarpe/agent-skills --skill amit-operator-commands-amitkarpe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Short operator phrases like "check td", "go td", "commit all", or "TTL cleanup" imply heavier multi-step workflows, and handling them ad hoc risks unsafe git mutations, unapproved worker dispatches, or accidental deletion of context and AWS resources. ## Core Features & Use Cases - Worker Command Routing: Resolves lane nicknames (check/prep/go/continue) against verified goal IDs, mappings, and approval state before any status read or dispatch. - Context and Handoff Management: Maintains CONTEXT.md and HANDOFF.md with compact, decision-grade restart packets instead of dated snapshot sprawl. - Safe Git and Cleanup Workflows: Provides guarded commit/push/merge flows plus local debris cleanup and read-only-first AWS TTL cleanup with explicit approval gates. - Use Case: When Amit types "go td", the skill verifies the exact approved goal and worker mapping, then dispatches only that goal via the native queue protocol rather than guessing from the newest file. ## Quick Start Ask the agent to handle the operator phrase "check td" and report the verified worker status without making any edits.

Frequently Asked Questions about amit-operator-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely dispatch a worker goal with a short command?▼

Use a phrase like "go td" only after the skill resolves one exact approved goal ID, goal path, and verified worker mapping. It submits via the native /goal queue protocol and never upgrades authority or guesses from the newest file.

What commands does this operator command router support?▼

It handles worker phrases like check/prep/go/continue, context commands like save context, save handoff, and clear context, plus git workflows (commit all, push all, merge) and cleanup including AWS TTL cleanup.

Does "approved" automatically run or merge work?▼

No. Approval must bind unambiguously to the resolved goal and requested action; otherwise the skill stops and reports the missing target or approval. Bulk phrases like "approved for all" never trigger inferred dispatches.

How does TTL cleanup avoid deleting the wrong AWS resources?▼

It starts read-only, loads ~/.agent/AWS.md, inventories tagged resources, and saves evidence under ~/.AGENTS-temp/<repo>/. Deletion happens only for the explicitly approved candidate set, followed by verification.

When should I not use this skill for shortcuts like "next"?▼

When the repo's global AGENTS.md already defines simple shortcuts like next, save context, or save handoff, those should be handled from current repo truth with minimal context instead of loading this heavier routing skill.