coding-engineer-skills

Plugin coding-engineer-skills from marketplace cogine-ai in cogine-ai/marketplace. Commands read from the repo's manifest — today.

Skills (29)

• ai-app-security-audit

  Audit AI and LLM apps for concrete security, tool, prompt, key, cost, and supply-chain risks.

• backlog-ready-spec

  Turn ambiguous product or bug requests into de-duplicated, implementation-ready specs with acceptance criteria and validation.

• code-review

  Review committed changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports

• codebase-design

  Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

• cogine-multirepo-worker

  Use for Cogine's classic one-worker-per-repository control plane; use cogine-orchestrator for shared WORK/TEST lanes.

• cogine-orchestrator

  Use for Cogine's WORK/TEST multi-repository control plane with per-repo work and shared independent verification.

• cogine-power-gates

  Use for gate or blind-spot reviews, consequential actions, or material uncertainty, deviation, or missing proof that changes whether work can proceed.

• devex-review

  Audit implemented APIs, CLIs, SDKs, MCP servers, plugins, docs, or onboarding for real developer friction.

• diagnosing-bugs

  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

• domain-modeling

  Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

• fix-ci

  Find failing PR checks, inspect logs or external check links, and apply focused fixes

• frontend-design

  Create distinctive, intentional frontend UI without generic visual defaults.

• good-offence

  Review unnecessary defensive implementations, including duplicate validation, unreachable guards, catch/sentinel cascades, and unjustified retry or fallback layers. Use for good offence or defensive-complexity review. Produces suggestions rather than code changes.

• grilling

  Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

• improve-codebase-architecture

  Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

• local-ultra-review

  Use only when explicitly asked for a high-confidence, read-only local or PR code review.

• loop-on-ci

  Explicitly monitor PR checks and fix failures until green, using gh pr checks as the source of truth for PR-attached checks.

• plan-devex-review

  Review a developer-facing API, CLI, SDK, MCP, plugin, docs, or onboarding plan before implementation.

• planmode-engineer

  Review an execution plan for architecture, data flow, edge cases, tests, and performance.

• review-and-ship

  Explicitly run final self-review and shipping for a completed task branch, including verification, commit, push, and pull-request preparation.

• run-smoke-tests

  Run Playwright smoke tests, debug failures, and verify fixes

• security-best-practices

  Perform explicitly requested secure-coding or security reviews for Python, JavaScript/TypeScript, or Go.

• setup-matt-pocock-skills

  Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

• shadcn

  Build, style, debug, or update shadcn/ui components and projects using current CLI guidance.

• tdd

  Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

• to-spec

  Explicitly synthesize the current conversation into a PRD or spec and publish it to the configured tracker.

• to-tickets

  Explicitly split a plan or spec into tracer-bullet tickets with blocking edges on the configured tracker.

• vercel-react-best-practices

  Apply performance-oriented React and Next.js guidance to components, data fetching, rendering, and bundles.

• worktree-management

  Create, use, and safely retire an isolated Git worktree for coding changes. Use when the user requests a worktree or isolation, the current checkout is dirty, parallel branches or agents need separation, or a large or risky change should not disturb the current workspace. Do not use for read-only wo

Similar plugins