erne-worker
- Repo stars 36
- License MIT
- Author updated Live
- Author repo everything-react-native-expo
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- 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 special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: erne-worker
description: ERNE — Autonomous ticket execution — polls a provider, picks up ready tickets, and runs the full…
category: engineering
runtime: no special runtime
---
# erne-worker output preview
## PART A: Task fit
- Use case: ERNE — Autonomous ticket execution — polls a provider, picks up ready tickets, and runs the full ERNE pipeline (validate, plan, code, test, review, PR). erne worker --config <path-to-worker.json> requires Vendor-specific API key. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Usage / Options / Pipeline Steps” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “ERNE — Autonomous ticket execution — polls a provider, picks up ready tickets, and runs the full ERNE pipeline (validate, plan, code, test, review, PR). erne worker --config <path-to-worker.json> requires Vendor-specific API key. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Usage / Options / Pipeline Steps” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; may access external network resources; requires Vendor-specific API keys.
## Running Rules
- read files, write/modify files, run shell commands; may access external network resources; requires Vendor-specific API keys.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/erne-worker`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Usage / Options / Pipeline Steps”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: erne-worker
description: ERNE — Autonomous ticket execution — polls a provider, picks up ready tickets, and runs the full…
category: engineering
source: JubaKitiashvili/everything-react-native-expo
---
# erne-worker
## When to use
- ERNE — Autonomous ticket execution — polls a provider, picks up ready tickets, and runs the full ERNE pipeline (valida…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Usage / Options / Pipeline Steps” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; may access external network resources; requires Vendor-specific API keys.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "erne-worker" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Usage / Options / Pipeline Steps
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | may access external network resources
guardrails -> requires Vendor-specific API keys + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}/erne-worker — Autonomous Ticket Execution
Usage
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
- 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
- Execute — Run Claude Code in an isolated git worktree
- Test — Run test suite, verify no regressions
- Self-Review — Automated code review against ERNE standards
- Health Delta — Compare audit score before/after
- 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, filtersrepo— Local path, base branch, remoteerne— Hook profile, quality gates, confidence thresholdlog— File path and log level
Examples
# 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
Decide Fit First
Design Intent
How To Use It
Boundaries And Review