everything-leader

Plugin everything-leader in tarasov46/codex-everything-leader. Commands read from the repo's manifest — 1 month ago.

Skills (12)

• architecture-rfc

  Design a technical approach before implementation. Use when Codex needs to compare options, define interfaces, plan migrations, split work, or create an architecture note for a meaningful codebase change.

• bug-hunt

  Diagnose and fix bugs in a codebase. Use when Codex needs to reproduce a failure, trace likely causes, inspect related code paths, implement a fix, add regression coverage, and verify behavior.

• code-review

  Review code changes for bugs, regressions, missing tests, maintainability risks, and behavioral mismatches. Use when Codex is asked to review a diff, branch, pull request, or recently edited code.

• codebase-memory

  Use codebase-memory-mcp or another code knowledge graph to inspect structure, call chains, routes, blast radius, dead code candidates, and architectural communities before editing a repository.

• delivery-workflow

  Reproduce a complete high-quality development task lifecycle. Use when Codex is asked to build, change, debug, review, harden, or ship something end to end, especially in an everything-leader attached project where the user expects discovery, planning, implementation, validation, security checks, an

• docs-researcher

  Verify external APIs, libraries, frameworks, tools, and current documentation before implementation. Use when Codex needs up-to-date or version-specific technical facts from primary sources.

• feature-builder

  Implement a feature end to end in an existing codebase. Use when Codex needs to turn a requirement into scoped code changes, tests, validation, and a clear summary while following repo conventions.

• project-bootstrap

  Create, prepare, or attach everything-leader to a selected project folder. Use when the user asks from the everything-leader hub to create/start a new project at a path, or asks inside a target project to connect, enable, prepare, bootstrap, or install everything-leader for that project. Seeds proje

• repo-onboarding

  Map and understand an unfamiliar codebase before making changes. Use when Codex needs to inspect project structure, build/test commands, architecture, dependencies, conventions, risks, or where to implement a requested change.

• security-baseline

  Run a security baseline for generated or modified code using ready-made scanners and Codex security tooling. Use when Codex needs to check a repository, feature branch, plugin, skill, MCP setup, dependency set, or vibe-coded project before merge, release, sharing, or installation.

• security-pass

  Review code, configuration, or a planned change for security risks. Use when Codex needs to inspect authentication, authorization, secrets, injections, unsafe file operations, supply-chain risks, or sensitive data handling.

• test-repair

  Investigate and repair failing tests, linters, type checks, CI jobs, or validation commands. Use when Codex needs to read failures, identify root causes, fix code or tests, and rerun focused checks.

Similar plugins