erne worker

Engineering Community

Skill notes

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

Poll — Fetch ready tickets from the configured provider Validate — Check ticket has enough detail (title, description, acceptance criteria) Confidence Score — Estimate likelihood of autonomous success (0-100) Context Resolve — Load project stack, audit data, and relevant files Plan — Generate implementation plan from ticket + context

Supported Providers

clickup — ClickUp tasks (API token + list ID) github — GitHub Issues (repo + labels) linear — Linear issues (API key + team) jira — Jira issues (API token + project) local — JSON file with ticket definitions (for testing)

Configuration Reference

See worker.example.json at the project root for a full example. Key sections: provider — Type, credentials, poll interval, filters repo — Local path, base branch, remote erne — Hook profile, quality gates, confidence threshold log — File path and log level

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@JubaKitiashvili · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · Vendor-specific
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# /erne-worker — Autonomous Ticket Execution

## Usage

```bash
erne worker --config <path-to-worker.json>
```

## 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 data, and relevant files
5. **Plan** — Generate implementation plan from ticket + context
6. **Execute** — Run Claude Code in an isolated git worktree
7. **Test** — Run test suite, verify no regressions
8. **Self-Review** — Automated code review against ERNE standards
9. **Health Delta** — Compare audit score before/after
10. **PR** — Create pull request with full summary and link to ticket

## Supported Providers

- **clickup** — ClickUp tasks (API token + list ID)
- **github** — GitHub Issues (repo + labels)
- **linear** — Linear issues (API key + team)
- **jira** — Jira issues (API token + project)
- **local** — JSON file with ticket definitions (for testing)

## Configuration Reference

See `worker.example.json` at the project root for a full example. Key sections:

- `provider` — Type, credentials, poll interval, filters
- `repo` — Local path, base branch, remote
- `erne` — Hook profile, quality gates, confidence threshold
- `log` — File path and log level

## Examples

```bash
# 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
```

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.