Wire new capabilities into public surfaces after unit tests complete.
npx skills add https://github.com/Kohlex/autopilot-plugin --skill integrate-kohlex
Please help me install this Agent Skill. Skill: integrate Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/integrate Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill integrate-kohlex
Wire new capabilities into the project's public surface after unit tests complete, ensuring they are reachable through the established interfaces without invasive edits.
Run /integrate in the capability worktree after PLAN.md is complete to wire the new module into the project's public surface.
High-intent search queries and answers about installing and using this skill.
To wire a new module into your project's public surface, you can run an integration command after unit tests complete. It reads your ARCHITECTURE.md §3 to mirror established wiring conventions from sibling modules into the designated wiring files.
You need ARCHITECTURE.md, a completed PLAN.md, and a SPEC.md to prove reachability before integrating a new capability. These input requirements ensure the integration process correctly mirrors established wiring patterns for HTTP routes, CLI dispatchers, or Tauri commands.
The integration process edits only designated wiring files and updates SPEC.md breadcrumbs, producing a single cohesive integration commit. This ensures that module barrels and wiring files across event buses, library exports, or workflows are updated atomically.
Yes, you can automate wiring capabilities into Tauri commands and library exports. The integration process applies across HTTP routes, CLI dispatchers, event buses, and workflows by detecting the integration shape from ARCHITECTURE.md and mirroring sibling module patterns.
Capability integration requires PLAN.md completion and SPEC.md reachability to enforce input requirements and validate the new module. This ensures the wiring process only runs after the capability is built and ready to be mirrored into the public surface without invasive edits.
Yes, the public surface integration is limited to editing only designated wiring files and updating SPEC.md breadcrumbs. It avoids invasive edits by mirroring established wiring conventions from sibling modules, ensuring the new capability is reachable through existing interfaces.
josemlopezAnalyze local threat model JSON and YAML files to output a structured security status summary.
kitfunsoAutomate Playwright smoke tests to verify page load and navigation.
dchukRun mock-based unit tests and WebDriver E2E tests for Tauri v2 apps.
usetheodevConfirms new public exports have production callers, integration tests, runtime metrics, and valid wiring declarations.
