Task-based pick
Code review
Tools that give an agent review discipline: break down the change, find weak spots, check style and architecture instead of just praising. For developers and tech leads. Every entry states what it reads in your project and its risk level.
12 tools
Tools in this pick
A completion-discipline skill for large agent tasks: write the acceptance ledger with runnable checks first, then do the work, then reverify against evidence
Two skills for coding agents: wtf audits a project before shipping, better-codex keeps the agent disciplined while working on code
Guard skills for coding agents: a second pass over the diff that catches typical AI mistakes in code, tests and docs
A skill that explains and audits code, telling you what it does and why instead of just accepting it
A code review skill across many languages and frameworks: architecture, performance, security, anti-patterns and common bugs
Agents Best Practices
agents-best-practices
A provider-neutral skill for designing agent systems: loop architecture, tools, permissions, memory and observability
A multi-agent harness that verifies results by artifacts: stop hooks, an independent judge and an event log for Claude Code, Codex, Cursor and more
Tech Leads Club Agent Skills
Agent Skills
A vetted skill registry with a CLI that installs into twenty-plus agents and an MCP server for on-demand skill lookup
A tool that builds tested skills from a real workflow and governs their lifecycle through your own marketplace
A skill for second-agent review of plans or code: Claude Code starts rounds, Codex reviews, and they exchange files
An autonomous iteration skill for agents: modify, verify, revert failed changes, and repeat the loop toward a target metric
A skill plus hooks that keep a coding agent on task and cut speculative defenses, unread checksums and scope creep
FAQ
Does it replace human review?
No. The agent catches routine issues and drafts comments, but the decision and context stay with a person.
Will the agent see all my code?
It depends on the tool. Check the risk level and the file access note in each entry.
Collect these tools into a pack and share with one link.