mikode-skills

Plugin mikode-skills from marketplace mikode in Mikode13/skills. Commands read from the repo's manifest — 1 month ago.

Skills (12)

• adr-accept

  Accept a proposed MiKode ADR - flip statuses, activate the related standard, update all indexes, handle supersession, and finish an approved Draft pull request consistently. Use when the user confirms a proposed decision should become accepted.

• adr-new

  Create a new Architecture Decision Record in the MiKode engineering repository through a guided interview and a protected Draft pull request. Use when the user wants to discuss, document, propose, or record a cross-project technical decision and review it before it can be merged.

• mikode-architecture-review

  Review architecture in selected code, modules, local changes, or pull requests. Activate for boundaries, public contracts, dependency direction, persistence or data flow, provider integrations, cross-cutting abstractions, or documented architecture decisions; use the project's architecture document

• mikode-code-philosophy-review

  Review code against the MiKode coding philosophy. Use after implementation or refactoring to identify correctness issues, architectural coupling, unnecessary complexity, weak tests, avoidable technical debt, scope creep, and generated-code patterns. When architecture or security is the primary conce

• mikode-code-philosophy

  Apply the MiKode coding philosophy when implementing, modifying, or refactoring code. Use when an agent writes production code in a MiKode project and should prioritize strategic design, explicit behaviour, strong boundaries, maintainability, and meaningful tests over speed or generated-code verbosi

• mikode-context

  Resolve current MiKode policy for a task or explain relevant decision history. Use when applicable standards are unknown, the user asks about MiKode policy or decisions, or another skill delegates a policy lookup. Routine local work with resolved policy does not need another lookup.

• mikode-documentation

  Create, update, or review MiKode technical documentation using the current documentation policy from Mikode13/engineering. Use for READMEs, supporting docs, project decision records, or documentation work delegated by another skill when placement, structure, clarity, duplication, current-state accur

• mikode-init

  Create a new MiKode repository from scratch using the latest accepted engineering policy. Use when the user wants to start, bootstrap, or scaffold a MiKode repository while keeping the current TypeScript/Node/pnpm defaults for code projects and avoiding runtime tooling for content-only repositories.

• mikode-review

  Review a pull request or local change against its issue or change contract, implementation plan, and repository behavior. Use for a complete review requested from chat, a harness, or CI; coordinate five perspectives, load specialist guidance by risk, verify findings, and return clean, suggestions, c

• mikode-router

  Select and order the minimum MiKode skills for a task before loading their bodies. Use when asked to route MiKode work, when several workflows could apply, or when trusted agent guidance delegates skill selection. A clearly selected domain skill can run directly.

• mikode-security-review

  Review selected code, a module, local changes, or a pull request for exploitable security defects and unsafe defaults. Activate for authentication or authorization, secrets and sensitive data, untrusted input or execution, network boundaries and external services, dependencies and supply chain, CI w

• standards-check

  Audit a MiKode repository or a requested change against current applicable engineering standards. Use before committing or on demand to report verified deviations, missing evidence, and the exact audit scope without forcing unrelated tooling onto the project.

Similar plugins