contribute-to-eliza

Implements or reviews scoped elizaOS GitHub issues and pull requests with verified evidence.

19.2k|5.7k|Updated Jul 9, 2024
One-click install
npx skills add https://github.com/elizaOS/eliza --skill contribute-to-eliza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contribute-to-eliza
Source: https://github.com/elizaOS/eliza/tree/main/packages/skills/skills/contribute-to-eliza
Command: npx skills add https://github.com/elizaOS/eliza --skill contribute-to-eliza

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Contributing to a large open-source monorepo like elizaOS requires finding unclaimed work, following strict repository conventions, producing verifiable proof of behavior, and safely handling untrusted pull request code. This Skill guides an agent through the entire contribution lifecycle so submissions meet maintainer standards without self-approval or fabricated evidence.

Core Features & Use Cases

  • Issue completion workflow: Claims one scoped, contributor-ready issue, implements the change on a correctly prefixed branch, adds real tests, runs repository verification, and captures rubric-compliant evidence before opening a PR against develop.
  • Independent PR review and repair: Inspects an open PR from a trusted checkout, reproduces behavior inside a disposable sandbox, leaves actionable findings, and applies authorized minimal repairs with missing tests.
  • Candidate inventory report: Runs scripts/live-report.mjs to paginate GitHub issues and PRs, filtering out claimed, blocked, sensitive, bot-authored, or already-reviewed work.
  • Use Case: An agent selects an unclaimed bug-confirmed issue, implements the fix, runs bun run verify, attaches screenshots and logs to the PR evidence rows, and moves the Project card to Needs-agent-verify for independent review.

Quick Start

Use the contribute-to-eliza skill to find one unclaimed elizaOS issue and take it through implementation, testing, and evidence-backed PR submission.

Frequently Asked Questions about contribute-to-eliza

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

FAQPage Schema
How do I contribute to the elizaOS repository as an AI agent?

Run the live-report.mjs script to inventory unclaimed issues or PRs, claim one with a public CLAIMING comment, implement or review the change following repository AGENTS.md guidance, and submit a PR with complete evidence rows against the develop branch.

How do I safely review an untrusted pull request on GitHub?

Fetch the exact PR head SHA without checking it out, audit the diff for lifecycle hooks and executable changes, then run builds and tests only inside a fresh disposable container with no credentials, no network, and bun install --frozen-lockfile --ignore-scripts.

What evidence is required for an elizaOS pull request?

The PR template requires seven rows: before and after screenshots, a walkthrough video, backend logs, frontend logs, a real-LLM trajectory, and domain artifacts. Each row needs concrete attachments or a specific N/A reason; placeholders are rejected.

Can I run PR tests that need network access or credentials?

Only with explicit operator approval in a separate single-use sandbox with allowlisted egress and an ephemeral least-privilege credential. Never pass through the agent's normal gh token, and revoke the test credential immediately afterward.

What GitHub CLI version does the live-report script support?

The script supports GitHub CLI 2.45 and later. It uses gh api --paginate --jq '.[]' to emit newline-delimited JSON records instead of relying on the newer --slurp flag, and fails closed on malformed or truncated output.