From erne-universal
Polls configured ticket providers for ready tickets and runs full ERNE pipeline: validate, plan, code in git worktree, test, review, and create PRs.
How this command is triggered — by the user, by Claude, or both
Slash command
/erne-universal:erne-workerThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /erne-worker — Autonomous Ticket Execution ## Usage ## Options | Flag | Description | |------|-------------| | `--config <path>` | Path to worker configuration JSON (required) | | `--dry-run` | Fetch tickets and print them without executing | | `--once` | Process one ticket and exit | ## Pipeline Steps 1. **Poll** — Fetch ready tickets from the configured provider 2. **Validate** — Check ticket has enough detail (title, description, acceptance criteria) 3. **Confidence Score** — Estimate likelihood of autonomous success (0-100) 4. **Context Resolve** — Load project stack, audit dat...
erne worker --config <path-to-worker.json>
| Flag | Description |
|---|---|
--config <path> | Path to worker configuration JSON (required) |
--dry-run | Fetch tickets and print them without executing |
--once | Process one ticket and exit |
See worker.example.json at the project root for a full example. Key sections:
provider — Type, credentials, poll interval, filtersrepo — Local path, base branch, remoteerne — Hook profile, quality gates, confidence thresholdlog — File path and log level# Dry run to see available tickets
erne worker --config worker.json --dry-run
# Process one ticket and stop
erne worker --config worker.json --once
# Continuous polling mode
erne worker --config worker.json
npx claudepluginhub jubakitiashvili/everything-react-native-expo/workflowInterprets natural language requests to run or inspect ai-workflow pipelines for Linear tickets, supporting triage, implementation, status checks, and more.
/developSpawns orchestrator subagent to autonomously implement ticket via triage-plan-code-review-QA-PR workflow, creates git worktree if needed, updates ticket status.
/execute-ticketExecutes a Jira ticket by fetching its implementation plan, verifying completeness, exploring the codebase, and running implementation steps with parallel execution support.
/do-issueImplements GitHub/GitLab/Bitbucket issues using progressive analyze-specify-plan-implement-validate-complete workflow with optional step skipping, scope detection, dry-run, and multi-issue support.
/issue-createCreates a new ticket/issue in configured backend (Gitea, GitHub, Jira, Linear, or local files) with title, optional description, labels, assignee, priority, milestone, and regression check. Returns issue number, URL, or file path.
/work-on-monolithicRuns the full issue lifecycle — investigate, build, review, merge, close — within a single prompt session. Reads forge.yaml for project configuration and supports multi-repo routing.