engineer-augmentor

Plugin engineer-augmentor from marketplace augmentor-packs in Krosebrook/augmentor-packs. Commands read from the repo's manifest — today.

Skills (8)

• client-key-exposure-check

  Use when the user builds a front-end, browser extension, mobile app, static site, or prototype that calls a paid or privileged API. Finds API keys and secrets exposed to the client, explains the risk, and outlines a fail-closed server-side proxy pattern with rate limits and origin checks. Reviews an

• debugging-coach

  Use when the user is stuck on a bug, flaky behavior, or unexplained failure. Runs a hypothesis-driven investigation: reproduce, gather evidence, rank hypotheses, design the cheapest discriminating experiment, and confirm the root cause before any fix. Coaches the method; never guesses a fix as fact.

• failing-test-triage

  Use when a test suite has failures and the user wants to understand and fix them efficiently. Groups failures by shared root cause, orders them by dependency, and fixes or proposes fixes one group at a time, deciding whether the test or the code is wrong. Never deletes or weakens tests to go green.

• logic-audit

  Use when the user wants code checked for logical errors before they become bugs: control-flow gaps, unhandled states, off-by-one and boundary errors, data contract mismatches, race conditions, and silent failure paths. Reads and reasons; reports findings with evidence and test cases to prove them.

• pre-build-spec

  Use before starting a feature, script, service, or refactor. Produces a short pre-build spec: problem, scope and non-goals, interfaces and data, edge cases, risks, test plan, rollout and rollback, and open questions. Interviews for missing facts and marks them; does not start coding until the user a

• review-feedback-planner

  Use when the user receives code review comments or PR feedback and wants to process them systematically. Parses each comment, classifies it (bug, design, style, question, nit), proposes a response and change plan, flags disagreements to discuss, and checks nothing is missed. Drafts replies; the user

• script-red-team

  Use when the user writes or reviews a Bash or PowerShell script, automation job, or one-liner that will run on real systems. Adversarially reviews for safety: quoting, error handling, idempotency, destructive operations, secrets handling, privilege, and portability, with a dry-run plan. Reviews and

• task-decomposer

  Use when a request or project is large, multi-part, or ambiguous. Breaks it into workstreams and tasks with dependencies, identifies what can run in parallel, defines done for each, and plans the integration and verification step. The user assigns and executes.

Slash commands (4)

• /engineer-augmentor:audit-logic

  Audit a file or diff for logical errors with test cases

• /engineer-augmentor:debug

  Hypothesis-driven debugging session for a stuck bug

• /engineer-augmentor:review-plan

  Turn PR review comments into a change plan and reply drafts

• /engineer-augmentor:spec

  Write a pre-build spec before coding

Subagents (2)

• logic-auditor

  Read-only logic auditor. Reads the specified files or recent diff and reports logical errors (boundaries, unhandled states, data contract mismatches, races, swallowed errors) with file:line evidence and a test case per finding. Use before merging risky changes.

• script-reviewer

  Read-only adversarial reviewer for Bash and PowerShell scripts. Flags unquoted expansions, unsafe deletes, missing error handling, non-idempotent steps, hard-coded secrets, and privilege issues, and runs shellcheck/PSScriptAnalyzer if available. Use before running a script on real systems.

Similar plugins