Lfg
Skill ActiveRun the full autonomous engineering pipeline end-to-end (plan, work, code review, test, commit, push, open PR, watch CI, fix CI failures until green). Use only when the user explicitly requests hands-off execution of a software task and provides a feature description; do not auto-route casual conversation here.
To automate the full software development lifecycle, ensuring code quality and efficient delivery through a hands-off, end-to-end pipeline.
Features
- Automated planning and task breakdown
- End-to-end code execution and review
- Automated testing and CI integration
- Commit, push, and PR management
- Automated fixing of CI failures
Use Cases
- When a user explicitly requests hands-off execution of a software development task.
- To fully automate the process of implementing a new feature from description to green CI.
- For managing complex code review cycles and ensuring adherence to quality standards.
Non-Goals
- Handling casual conversation or non-software related tasks.
- Manual intervention in the development pipeline once initiated.
- Auto-routing unrelated user requests to this pipeline.
Trust
- warning:Issues AttentionThe project had 25 issues opened and 115 closed in the last 90 days, resulting in a closure rate below 50% (approx. 19.6%), indicating slower than ideal response times for open issues.
Installation
First, add the marketplace
/plugin marketplace add EveryInc/compound-engineering-plugin/plugin install compound-engineering@compound-engineering-pluginQuality Score
Trust Signals
Similar Extensions
ClawSweeper Skill
100Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, commit-review reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions monitoring, permissions, gates, and manual backfills.
Oh My Claudecode
100Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.
Github
100Use gh for GitHub issues, PR status, CI/logs, comments, reviews, releases, and API queries.
Openclaw Testing
100Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
Claude Handoff
100Run /handoff to capture session data, then write a phased implementation plan that references it. Creates beads for tracking.