@mknrt/autotests-overkill 1.1.0

package/package.json

@@ -0,0 +1,73 @@
+{
+  "name": "@mknrt/autotests-overkill",
+  "version": "1.1.0",
+  "private": false,
+  "type": "module",
+  "description": "AI-assisted testing intelligence platform for autotests2, caseplatform-web, and CI artifacts",
+  "license": "MIT",
+  "author": "mknrt",
+  "homepage": "https://github.com/iamknrt/autotests-overkill#readme",
+  "bugs": {
+    "url": "https://github.com/iamknrt/autotests-overkill/issues"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/iamknrt/autotests-overkill.git"
+  },
+  "engines": {
+    "node": ">=20.0.0"
+  },
+  "bin": {
+    "autotests-overkill": "./dist/src/cli/main.js"
+  },
+  "files": [
+    "dist/",
+    "skills/",
+    "templates/",
+    "assets/",
+    "docs/",
+    "overkill.config.example.json",
+    "README.md"
+  ],
+  "exports": {
+    ".": {
+      "import": "./dist/src/index.js",
+      "types": "./dist/src/index.d.ts"
+    }
+  },
+  "main": "./dist/src/index.js",
+  "types": "./dist/src/index.d.ts",
+  "publishConfig": {
+    "access": "public"
+  },
+  "scripts": {
+    "clean": "node -e \"require('fs').rmSync('dist', { recursive: true, force: true })\"",
+    "build": "npm run clean && tsc -p tsconfig.build.json",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "lint": "tsc -p tsconfig.json --noEmit",
+    "index": "tsx src/cli/indexKnowledge.ts",
+    "mcp": "tsx src/cli/runMcpServer.ts",
+    "mcp:smoke": "vitest run tests/mcp/smoke.test.ts",
+    "acceptance:coverage": "tsx src/cli/runAcceptance.ts coverage",
+    "acceptance:coverage:legacy": "tsx src/cli/runAcceptance.ts coverage dateRangeInput",
+    "acceptance:blueprint": "tsx src/cli/runAcceptance.ts blueprint dateRangeField",
+    "acceptance:failure": "tsx src/cli/runAcceptance.ts failure",
+    "acceptance:impact": "tsx src/cli/runAcceptance.ts impact",
+    "verify": "npm run lint && npm run test && npm run build",
+    "prepublishOnly": "npm run verify"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.13.0",
+    "better-sqlite3": "^12.6.2",
+    "fast-glob": "^3.3.3",
+    "zod": "^3.24.1"
+  },
+  "devDependencies": {
+    "@types/better-sqlite3": "^7.6.12",
+    "@types/node": "^22.15.3",
+    "tsx": "^4.19.4",
+    "typescript": "^5.8.3",
+    "vitest": "^3.1.2"
+  }
+}

package/skills/overkill-debug-failure/SKILL.md

@@ -0,0 +1,13 @@
+# overkill-debug-failure
+
+Goal: triage failed runs using real artifacts and metadata.
+
+Workflow:
+1. Run `summarize_ci_context`.
+2. Run `triage_failed_run`.
+3. Run `build_rerun_scope`.
+4. If code changed recently, run `analyze_diff_impact`.
+
+Rules:
+- Separate artifact-backed hypotheses from generic guesses.
+- Mention screenshots, videos, or API captures explicitly when they inform the conclusion.

package/skills/overkill-find-gaps/SKILL.md

@@ -0,0 +1,13 @@
+# overkill-find-gaps
+
+Goal: show meaningful coverage gaps without hand-grepping two repositories.
+
+Workflow:
+1. Run `map_feature_to_existing_coverage`.
+2. Run `find_frontend_runtime_logic`.
+3. Run `analyze_test_gaps`.
+4. Run `recommend_selector_strategy` if the next step is new test work.
+
+Rules:
+- Focus on runtime branches, methods, and events with evidence.
+- Distinguish true gaps from unclear heuristics using warnings/confidence.

package/skills/overkill-generate-setup/SKILL.md

@@ -0,0 +1,12 @@
+# overkill-generate-setup
+
+Goal: produce a setup/teardown plan that respects `autotests2` conventions.
+
+Workflow:
+1. Run `find_test_area_context`.
+2. Run `find_existing_test_assets`.
+3. Run `build_setup_teardown_plan`.
+
+Rules:
+- Reuse auth, init, and wait helpers before suggesting new support code.
+- Keep setup deterministic and aligned with the target area.

package/skills/overkill-generate-test/SKILL.md

@@ -0,0 +1,15 @@
+# overkill-generate-test
+
+Goal: generate a draft test with maximum reuse and minimum ad-hoc Cypress code.
+
+Workflow:
+1. Run `find_existing_test_assets`.
+2. Run `find_frontend_contract`.
+3. Run `find_frontend_runtime_logic`.
+4. Run `generate_spec_blueprint`.
+5. Present the draft as a starting point, not an auto-applied change.
+
+Rules:
+- Prefer existing commands, selectors, and init patterns from `autotests2`.
+- Do not silently write into consumer repositories.
+- Cite repo paths from evidence when explaining the draft.

package/skills/overkill-impact-analysis/SKILL.md

@@ -0,0 +1,12 @@
+# overkill-impact-analysis
+
+Goal: determine which tests are affected by a code change.
+
+Workflow:
+1. Run `analyze_diff_impact`.
+2. Run `build_rerun_scope` if there are failed specs or current CI context.
+3. Summarize the smallest safe rerun set.
+
+Rules:
+- Prefer evidence-backed impacted specs over broad reruns.
+- Call out uncertainty with warnings when heuristics are weak.

package/skills/overkill-onboard/SKILL.md

@@ -0,0 +1,16 @@
+# overkill-onboard
+
+Goal: onboard an engineer to the platform quickly.
+
+Start Here:
+1. Read `README.md`.
+2. Copy `overkill.config.example.json` to `overkill.config.json`.
+3. Run `npm install`.
+4. Run `npm run build`.
+5. Run `npm run index`.
+6. Run `npm run mcp:smoke`.
+7. Use the checked-in `.mcp.json` manifest for client integration instead of `npm run mcp`, because stdio MCP servers must keep `stdout` clean.
+7. Run the acceptance commands against local repos.
+
+Key Idea:
+- The platform analyzes and drafts; it does not silently edit consumer repos.

package/skills/overkill-prompt-builder/SKILL.md

@@ -0,0 +1,13 @@
+# overkill-prompt-builder
+
+Goal: build high-quality prompts for Codex tasks on top of the platform.
+
+Prompt Template:
+1. State the target feature or widget.
+2. State the desired outcome: generate draft, find gaps, debug failure, or analyze impact.
+3. Mention the target area if known: `formRunner`, `constructor`, or `criticalPathTests`.
+4. Ask for evidence-backed output with repo paths.
+5. Ask explicitly to reuse existing assets before proposing new code.
+
+Example:
+`Use overkill tools to analyze the caption widget in formRunner, find reusable test assets, extract the frontend contract, and produce a draft spec skeleton with repo-path evidence.`

package/skills/overkill-reuse-project-patterns/SKILL.md

@@ -0,0 +1,13 @@
+# overkill-reuse-project-patterns
+
+Goal: reuse the project’s own commands, setup, and selector conventions before introducing anything new.
+
+Workflow:
+1. Run `find_existing_test_assets`.
+2. Run `find_test_area_context`.
+3. Run `recommend_selector_strategy`.
+4. Run `build_setup_teardown_plan` for the target area.
+
+Rules:
+- Prefer project helpers over custom chains.
+- Call out the exact paths to reusable assets.

package/skills/overkill-review-test-draft/SKILL.md

@@ -0,0 +1,10 @@
+# overkill-review-test-draft
+
+Goal: review a draft test for reuse, anti-flaky patterns, and project fit.
+
+Checklist:
+1. Confirm existing commands/helpers/selectors were reused where possible.
+2. Check that selector strategy is stable and aligned with `getWidget` or selectors tree.
+3. Check that setup uses `init()` or `initConf()` consistently.
+4. Compare the draft against `find_existing_test_assets` results for duplication.
+5. Flag brittle waits, DOM-order selectors, or silent mutations.

package/templates/prompts/debug-failure.md

@@ -0,0 +1,3 @@
+# Debug Failure Prompt
+
+Summarize CI stats, inspect screenshots/videos/API captures, then produce hypotheses grounded in artifacts. Separate environment/flaky suspects from probable product regressions.

package/templates/prompts/find-gaps.md

@@ -0,0 +1,3 @@
+# Find Gaps Prompt
+
+Map current coverage first, then compare runtime branches and events to the existing specs. Highlight only evidence-backed gaps and rank them by likely user impact.

package/templates/prompts/generate-test.md

@@ -0,0 +1,3 @@
+# Generate Test Prompt
+
+Use `find_existing_test_assets`, `find_frontend_contract`, `find_frontend_runtime_logic`, and `generate_spec_blueprint` for the target widget or feature. Reuse existing setup and selectors. Do not invent new helpers unless reuse is impossible.

package/templates/prompts/impact-analysis.md

@@ -0,0 +1,3 @@
+# Impact Analysis Prompt
+
+Given changed files or a diff, infer the frontend feature area, map to existing specs, and return the smallest rerun set that still protects the changed behavior.

package/templates/spec-blueprints/default.md

@@ -0,0 +1,39 @@
+# Default Spec Blueprint
+
+```js
+/**
+ * Draft spec blueprint
+ * Suggested import target: ../../../../../support/base
+ * Setup hints:
+ * - keep init(...) at describe level
+ * - reuse before()/beforeEach() from the closest reference spec
+ * Reuse candidates:
+ * - cy.getWidget
+ * - cy.selectForm / cy.selectAppInConstructor
+ * - cy.waitVcmForm / cy.waitFormsInFr
+ * Selector guidance: prefer existing selectors tree or testguid-backed hooks, not nth-child or deprecated elements selectors.
+ */
+import init from '../../../../../support/base';
+
+describe('[Overkill] <feature>', { tags: ['@vcm', '@regress', '@parallel-true'] }, () => {
+  init(Cypress.expose('<app-id>'));
+
+  before(() => {
+    cy.waitFormsInFr('<form count if the feature opens nested forms>');
+  });
+
+  beforeEach(() => {
+    cy.waitVcmForm();
+    cy.fixCypressSpec();
+    cy.selectForm('<form name from reference spec>');
+    cy.waitVcmForm();
+  });
+
+  const target = '<widget control name from reference spec>';
+
+  it('covers the primary scenario', () => {
+    cy.getWidget('<action widget from reference spec>').click();
+    cy.getWidget(target).should('be.visible');
+  });
+});
+```