repo-engine
Repo Engine
Purpose
Scan repositories, infer architecture, detect entry points, extract conventions, identify hotspots, and produce onboarding artifacts that accelerate future work.
Use When
- Onboarding into a repository or monorepo.
- Understanding architecture before making changes.
- Mapping entry points and execution flows.
- Extracting conventions and development hotspots.
- Producing agent-ready onboarding artifacts.
Avoid When
- The user already provided exact files for a small patch.
- Only code quality review is needed.
More from moeller-projects/agent-skillz
ado-gateway
Use when fetching Azure DevOps work items or pull request comments, parsing Azure DevOps pull request URLs, or normalizing read-only Azure DevOps data for downstream skills. Do not use when editing Azure DevOps state, reviewing GitHub pull requests, or authoring OpenSpec files.
4caveman
Trigger when user wants terse, low-token, high-signal technical replies for coding work. Avoid for documentation, onboarding, polished copy, or high-risk instructions requiring explicit detail.
3ops-engine
Use when designing CI/CD, reviewing infrastructure, working with containers or Kubernetes, or analyzing deployment and security risk. Avoid for pure application refactoring or documentation.
3doc-engine
Use when writing or improving README files, AGENTS.md guidance, architecture notes, or workflow documentation. Avoid when only implementation is requested.
3test-engine
Use when writing tests, improving coverage, designing E2E flows, or reducing flaky behavior in automation. Avoid when the task is pure refactoring with no testing component.
3thinking-engine
Use when a problem is vague, a plan needs critique, or options must be compared before execution. Avoid when implementation is already decided or direct execution is requested.
3