AUTO-5 - trckr

← AUTO-5

cli

Created: 2026-02-03 • Updated: 2026-02-03

Relationships Loading...

## Overview
Implement the core CLI commands for automation management using Click.

## Tasks
- [ ] Expand `automate.py` with Click CLI structure
- [ ] Implement commands:
  - `automate init` - Initialize database at ~/.automate/automate.db
  - `automate create --name --prompt --cwd --schedule [--model] [--max-budget] [--trckr-project-id] [--ntfy-topic]`
  - `automate list [--status] [--json]` - List all automations
  - `automate show <id>` - Show automation details
  - `automate pause <id>` - Set status to paused
  - `automate resume <id>` - Set status to active
  - `automate delete <id>` - Delete automation
- [ ] Add `--store` global option for custom database path
- [ ] JSON output support for scripting

## QA: Live Integration Testing

**Phase Gate 1 - Help Works:**
```bash
uv run python automate.py --help
```
✓ PASS: Shows help with all commands listed

**Phase Gate 2 - Init Creates Database:**
```bash
rm -f /tmp/test-automate.db
uv run python automate.py --store /tmp/test-automate.db init
ls -la /tmp/test-automate.db
```
✓ PASS: Database file exists

**Phase Gate 3 - Create Automation:**
```bash
uv run python automate.py --store /tmp/test-automate.db create \
  --name "Test Automation" \
  --prompt "echo hello world" \
  --cwd /tmp \
  --schedule "FREQ=DAILY;BYHOUR=9"
```
✓ PASS: Prints created automation ID (slug)

**Phase Gate 4 - List Automations:**
```bash
uv run python automate.py --store /tmp/test-automate.db list --json
```
✓ PASS: Returns JSON array with the created automation

**Phase Gate 5 - Show Automation:**
```bash
uv run python automate.py --store /tmp/test-automate.db show test-automation
```
✓ PASS: Shows automation details

**Phase Gate 6 - Pause/Resume:**
```bash
uv run python automate.py --store /tmp/test-automate.db pause test-automation
uv run python automate.py --store /tmp/test-automate.db show test-automation | grep -i status
# Should show "paused"
uv run python automate.py --store /tmp/test-automate.db resume test-automation
uv run python automate.py --store /tmp/test-automate.db show test-automation | grep -i status
# Should show "active"
```
✓ PASS: Status changes correctly

**Phase Gate 7 - Delete:**
```bash
uv run python automate.py --store /tmp/test-automate.db delete test-automation
uv run python automate.py --store /tmp/test-automate.db list --json
```
✓ PASS: List returns empty array

Pull Requests (comma-separated URLs)

Attachments

Comments (4)

qa-agent · 2026-02-03

## QA PASSED See QA report document: cacaae98-8aea-4d54-98a9-a825230c7280 **Summary:** - All 7 Phase Gates pass - All edge case hypotheses pass (duplicate names, special chars, unicode, long names, invalid RRULE, non-existent IDs) - Test suite: 31 passed, 93% coverage on automate.py - No regressions found Fix verified working.

agent · 2026-02-03

## Implementation Complete **Files Changed:** - `/home/nuc2/gitea/agent-automations/automate.py` - Complete CLI implementation - `/home/nuc2/gitea/agent-automations/tests/test_cli.py` - Comprehensive test suite **What was implemented:** 1. **CLI Commands:** - `init` - Initialize database at ~/.automate/automate.db - `create` - Create automation with name, prompt, cwd, schedule, and optional model/budget/trckr/ntfy settings - `list` - List automations with optional --status filter and --json output - `show` - Show automation details with optional --json output - `pause` - Set automation status to paused - `resume` - Set automation status to active (recalculates next_run) - `delete` - Delete automation with --force flag to skip confirmation 2. **Database Schema:** - `automations` table with id, name, prompt, status, next_run_at, last_run_at, cwds (JSON), rrule, model, max_budget, trckr_project_id, ntfy_topic, timestamps - `automation_runs` table for tracking execution history - Proper indexes on status, next_run_at, and automation_id 3. **Features:** - `--store` global option for custom database path - Slug-based IDs generated from automation names - RRULE scheduling via python-dateutil - JSON output support for scripting - Duplicate name handling (appends -2, -3, etc.) **Verification:** All 7 Phase Gates pass: - Phase 1: `--help` shows all 7 commands - Phase 2: `init` creates database file - Phase 3: `create` returns slug ID (e.g., test-automation) - Phase 4: `list --json` returns JSON array - Phase 5: `show` displays all automation fields - Phase 6: `pause`/`resume` correctly toggle status - Phase 7: `delete --force` removes automation, list returns empty Test Results: 61 tests pass (31 new CLI tests + 30 existing tests), 93% coverage on automate.py **Commit:** 12df30b (merged to main)

worker-AUTO-5 · 2026-02-03

Assigned to worker-AUTO-5 in worktree /tmp/agent-automations-AUTO-5

triage-agent · 2026-02-03

## Feature Triage Complete **Status:** NOT IMPLEMENTED **Summary:** This CLI needs to be built from scratch. The project currently contains only documentation and a sample database from the Codex app analysis. No Python code exists yet. **Implementation Location:** - New file: `/home/nuc2/gitea/agent-automations/pyproject.toml` - Project configuration - New file: `/home/nuc2/gitea/agent-automations/automate.py` - Click CLI with all 7 commands **Dependencies:** - `click>=8.1.0` - CLI framework - `python-dateutil>=2.8.0` - RRULE parsing **Reference Implementations:** - Follow `/home/nuc2/gitea/trckr/main.py` pattern closely - Database schema is documented in `docs/ANALYSIS.md` **Complexity:** Medium - Standard Click CLI with SQLite, well-documented patterns available in codebase See attached triage report for full details.