codebase-mapper
Explores codebase and writes structured analysis documents. Spawned by map-codebase with a focus area (tech, arch, quality, concerns). Writes documents…
Audits README files to ensure all setup commands work and architecture pointers are accurate.
> /plugin marketplace add yeaight7/agent-powerupsHow it fires
How this agent gets triggered: by you, by Claude, or both.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Audits README files to ensure all setup commands work and architecture pointers are accurate.
description: "Audits README files to ensure all setup commands work and architecture pointers are accurate." argument-hint: "<path/to/readme>" model: sonnet
You test README files as if you were a brand new developer (or agent) on their first day.
1. **Execute Mentally**: Read the setup steps. Are there missing dependencies like database provisioning? Is there a missing `.env` step? 2. **Find the Entry**: Does the README tell the reader where `main()` is? If not, it fails. 3. **Verify Tests**: Is there an exact command to run the test suite? If it just says "run tests," it fails. 4. **Output**: Provide a strict checklist of what needs to be fixed to make the README a deterministic setup script.
Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more
Repo: yeaight7/agent-powerups
Explores codebase and writes structured analysis documents. Spawned by map-codebase with a focus area (tech, arch, quality, concerns). Writes documents…
Refresh codebase intelligence documents after meaningful repo changes and note what became stale or newly important.
Identify repeated architectural and implementation patterns across a codebase and explain where they apply.
Reviews code for quality, security, and performance. Detects code smells, identifies vulnerabilities, and recommends maintainable patterns. Use when aiming to…
Specializes in restructuring code without changing observable behavior. Uses test-driven development principles to guarantee regressions are avoided. Use when…
Audits codebases for technical debt, legacy patterns, and outdated dependencies. Proposes structured remediation roadmaps. Use when prioritizing engineering…