agentsclimarketplace

Autocoder

Skill laird/agents/skills/autocoder

Use this skill for autonomous GitHub issue resolution, issue triage, regression-test failure handling, proposal review, blocked-issue review, worker monitoring, and continuous fix loops in repositories that use the autocoder workflow.From its SKILL.md

Install
npx -y skills add laird/agents --skill autocoder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, as published. Nobody here has run it

Autocoder

Use this skill when the user wants Codex to operate the repo's autonomous issue-resolution or worker-coordination workflow.

Start Here

  1. Read AGENTS.md first for repo rules.
  2. Use the workflow order in references/workflow-map.md.
  3. Use references/command-mapping.md when translating legacy Claude plugin commands.
  4. Prefer existing scripts over restating shell procedures.

Operating Rules

  • CONTEXT COMPACTION IS MANDATORY (NON-NEGOTIABLE). Before starting work on ANY new issue in a fix loop, you MUST clear/compact the session context (the Codex equivalent of Claude's /compact). Every issue, every time, no exceptions. Each issue starts from a fresh, compacted context; never carry over detailed investigation notes from a previous issue. Skipping this WILL exhaust the context window and crash the worker mid-issue. See "Context Management (MANDATORY)" in plugins/autocoder/commands/fix.md.
  • Prioritize: triage -> bugs -> regression failures -> approved enhancements -> proposals.
  • Respect blocking labels: needs-approval, needs-design, needs-clarification, too-complex.
  • Use plugins/autocoder/scripts/regression-test.sh for full regression runs when appropriate.
  • Use scripts/append-to-history.sh to log significant work.
  • Treat AGENTS.md as the primary configuration source; use CLAUDE.md only as legacy fallback.
  • If Compound Engineering ce-* skills are available in your environment, prefer them over superpowers:* and bare-name toolkit skills per the precedence table in the command protocol's Optional skill enhancements section.

When To Read More

Keep looking

Skills are one crate of 610,220. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.