code-ai-installer 2.5.0 → 3.0.0

package/locales/en/.agents/skills/cloud-infrastructure-security/agents/skill.yaml

@@ -1,23 +0,0 @@
-version: 1
-name: "cloud-infrastructure-security"
-display_name: "Cloud Infrastructure Security Review"
-description: "Cloud/Infra/CI/CD Security Review — IAM, secrets manager, network, logging/monitoring, supply chain, CDN/WAF, backup/DR."
-default_prompt: "Use $cloud-infrastructure-security when the task matches the \"Cloud Infrastructure Security Review\" skill."
-triggers:
-  - "cloud-infrastructure-security"
-  - "cloud infrastructure security"
-  - "Cloud Infrastructure Security Review"
-  - "Cloud/Infra/CI/CD Security Review — IAM, secrets manager, network, logging/monitoring, supply chain, CDN/WAF, backup/DR"
-capabilities:
-  - "cloud"
-  - "infrastructure"
-  - "security"
-tools: []
-invocation:
-  explicit: true
-  implicit: true
-localization:
-  default_locale: "en"
-  available_locales:
-    - "ru"
-    - "en"

package/locales/en/.agents/skills/code-review-checklist/SKILL.md

@@ -1,133 +0,0 @@
----
-name: code-review-checklist
-description: Universal review checklist — code quality, readability, testability, security, contracts, Definition of Done.
----
-
-# Skill: Universal Code Review Checklist
-
-Checklist for the Reviewer Agent or self-review before handoff.
-
-**Sections:**
-1. [When to use](#1-when-to-use)
-2. [Checklist](#2-checklist)
-3. [Reviewer's Output Format](#3-reviewer-output)
-4. [Anti-patterns](#4-anti-patterns)
-
----
-
-## 1. When to use
-
-Use this checklist *after* the Senior Full Stack developer has finished coding, but *before* passing the task to QA (Tester) or closing it.
-
-The Reviewer Agent uses this checklist as the primary framework.
-
----
-
-## 2. Checklist
-
-### 2.1 Definition of Done (DoD)
-
-| # | Check | Severity | Status |
-|---|-------|----------|--------|
-| REV-01 | PRD requirements are met (no missing scope) | 🔴 P0 | ☐ |
-| REV-02 | Code runs without crashing (no obvious syntax errors) | 🔴 P0 | ☐ |
-| REV-03 | UX Spec visually matched (no missing UI elements) | 🔴 P0 | ☐ |
-| REV-04 | No `console.log` or debug code left behind | 🟠 P1 | ☐ |
-
-### 2.2 Architecture & Contracts
-
-| # | Check | Severity | Status |
-|---|-------|----------|--------|
-| REV-05 | Code follows `$architecture-doc` layers | 🔴 P0 | ☐ |
-| REV-06 | API implementation matches `$api-contracts` exactly | 🔴 P0 | ☐ |
-| REV-07 | New data model (if any) is documented | 🟠 P1 | ☐ |
-| REV-08 | ADR created if a significant architectural choice was made | 🟠 P1 | ☐ |
-
-### 2.3 Code Quality & Best Practices
-
-| # | Check | Severity | Status |
-|---|-------|----------|--------|
-| REV-09 | ESLint / Type checking passes (no red squiggles) | 🔴 P0 | ☐ |
-| REV-10 | Meaningful variable/function naming (no `data1`, `temp`) | 🟠 P1 | ☐ |
-| REV-11 | JSDoc present for all functions | 🔴 P0 | ☐ |
-| REV-12 | Functions are short and focused (< 40 lines ideally) | 🟠 P1 | ☐ |
-| REV-13 | No magic numbers or hardcoded strings | 🟠 P1 | ☐ |
-| REV-14 | React: No useless re-renders, correct memoization | 🟠 P1 | ☐ |
-| REV-15 | Go: correct error handling (`if err != nil`), no hidden panics | 🔴 P0 | ☐ |
-
-### 2.4 Error Handling & Logging
-
-| # | Check | Severity | Status |
-|---|-------|----------|--------|
-| REV-16 | Errors are caught (try/catch or `.catch()`) and handled | 🔴 P0 | ☐ |
-| REV-17 | Error format follows contract (`{ error: { code, message } }`) | 🔴 P0 | ☐ |
-| REV-18 | Structured logging used for significant events (not just `console.error`) | 🟠 P1 | ☐ |
-
-### 2.5 Security Basics
-
-| # | Check | Severity | Status |
-|---|-------|----------|--------|
-| REV-19 | Inputs are validated against boundary schemas (e.g., Zod) | 🔴 P0 | ☐ |
-| REV-20 | Protected routes check Auth properly | 🔴 P0 | ☐ |
-| REV-21 | No secrets (API keys, passwords) in code or frontend bundle | 🔴 P0 | ☐ |
-| REV-22 | Safe HTML rendering (dangerouslySetInnerHTML only if sanitized) | 🔴 P0 | ☐ |
-
-### 2.6 Testing
-
-| # | Check | Severity | Status |
-|---|-------|----------|--------|
-| REV-23 | Unit tests written or updated for new logic | 🔴 P0 | ☐ |
-| REV-24 | Tests pass successfully | 🔴 P0 | ☐ |
-| REV-25 | Edge cases and error paths tested | 🟠 P1 | ☐ |
-
----
-
-## 3. Reviewer's Output Format
-
-If passing the review:
-
-```markdown
-# Code Review: Approved
-
-All checks passed.
-- **DoD:** Met
-- **Code Quality:** Good, proper TDD cycle used.
-- **Contracts:** API matches spec perfectly.
-
-**Next Action:** Handoff to Tester Agent.
-```
-
-If requesting changes:
-
-```markdown
-# Code Review: Changes Requested
-
-## P0 Blockers (Must Fix)
-- **REV-11 (JSDoc):** `calculateTotal()` in `src/utils/cart.js:45` is missing JSDoc.
-- **REV-19 (Security):** `POST /checkout` is missing Zod body validation.
-
-## P1 Recommendations (Should Fix)
-- **REV-13 (Code Quality):** Hardcoded tax rate `0.2` in `cart.js:52`. Extract to constant.
-- **REV-14 (React):** Define `fetchData` outside `useEffect` or wrap in `useCallback` in `Cart.tsx:20`.
-
-**Next Action:** Return to Senior Full Stack to fix P0/P1 issues.
-```
-
----
-
-## 4. Anti-patterns
-
-| ❌ Anti-pattern | ✅ Solution |
-|----------------|-----------|
-| **Rubber stamping** | Actually run `npm run test` or check the code logic. Don't just say "LGTM". |
-| **Nitpicking without P0/P1 labels** | Clearly separate blockers (P0) from stylistic suggestions (P2). |
-| **Ignoring the contract** | The code might be beautiful but if it returns HTTP 200 instead of 201 as per `$api-contracts`, it's a bug. |
-| **Skipping security checks** | Always check for input validation and auth boundaries. |
-
----
-
-## See also
-- `$api-contract-compliance-review` — Deeper dive into API contracts.
-- `$architecture-compliance-review` — Deeper dive into layer boundaries.
-- `$security-review` — Deeper dive into AppSec.
-- `$tests-quality-review` — Deeper dive into test quality.

package/locales/en/.agents/skills/code-review-checklist/agents/claude.json

@@ -1,19 +0,0 @@
-{
-  "name": "code-review-checklist",
-  "display_name": "Universal Code Review Checklist",
-  "description": "Universal review checklist — code quality, readability, testability, security, contracts, Definition of Done.",
-  "default_prompt": "Use $code-review-checklist when the task matches the \"Universal Code Review Checklist\" skill.",
-  "triggers": [
-    "code-review-checklist",
-    "code review checklist",
-    "Universal Code Review Checklist",
-    "Universal review checklist — code quality, readability, testability, security, contracts, Definition of Done"
-  ],
-  "capabilities": [
-    "code",
-    "review",
-    "checklist"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/code-review-checklist/agents/copilot.json

@@ -1,19 +0,0 @@
-{
-  "name": "code-review-checklist",
-  "display_name": "Universal Code Review Checklist",
-  "description": "Universal review checklist — code quality, readability, testability, security, contracts, Definition of Done.",
-  "default_prompt": "Use $code-review-checklist when the task matches the \"Universal Code Review Checklist\" skill.",
-  "triggers": [
-    "code-review-checklist",
-    "code review checklist",
-    "Universal Code Review Checklist",
-    "Universal review checklist — code quality, readability, testability, security, contracts, Definition of Done"
-  ],
-  "capabilities": [
-    "code",
-    "review",
-    "checklist"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/code-review-checklist/agents/gemini.json

@@ -1,19 +0,0 @@
-{
-  "name": "code-review-checklist",
-  "display_name": "Universal Code Review Checklist",
-  "description": "Universal review checklist — code quality, readability, testability, security, contracts, Definition of Done.",
-  "default_prompt": "Use $code-review-checklist when the task matches the \"Universal Code Review Checklist\" skill.",
-  "triggers": [
-    "code-review-checklist",
-    "code review checklist",
-    "Universal Code Review Checklist",
-    "Universal review checklist — code quality, readability, testability, security, contracts, Definition of Done"
-  ],
-  "capabilities": [
-    "code",
-    "review",
-    "checklist"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/code-review-checklist/agents/kimi.yaml

@@ -1,15 +0,0 @@
-name: "code-review-checklist"
-display_name: "Universal Code Review Checklist"
-description: "Universal review checklist — code quality, readability, testability, security, contracts, Definition of Done."
-default_prompt: "Use $code-review-checklist when the task matches the \"Universal Code Review Checklist\" skill."
-triggers:
-  - "code-review-checklist"
-  - "code review checklist"
-  - "Universal Code Review Checklist"
-  - "Universal review checklist — code quality, readability, testability, security, contracts, Definition of Done"
-capabilities:
-  - "code"
-  - "review"
-  - "checklist"
-tools: []
-implicit_invocation: true

package/locales/en/.agents/skills/code-review-checklist/agents/openai.yaml

@@ -1,8 +0,0 @@
-interface:
-  display_name: "Universal Code Review Checklist"
-  short_description: "Universal review checklist — code quality, readability, testability, security, contracts, Defin…"
-  default_prompt: "Use $code-review-checklist when the task matches the \"Universal Code Review Checklist\" skill."
-dependencies:
-  tools: []
-policy:
-  allow_implicit_invocation: true

package/locales/en/.agents/skills/code-review-checklist/agents/qwen.json

@@ -1,19 +0,0 @@
-{
-  "name": "code-review-checklist",
-  "display_name": "Universal Code Review Checklist",
-  "description": "Universal review checklist — code quality, readability, testability, security, contracts, Definition of Done.",
-  "default_prompt": "Use $code-review-checklist when the task matches the \"Universal Code Review Checklist\" skill.",
-  "triggers": [
-    "code-review-checklist",
-    "code review checklist",
-    "Universal Code Review Checklist",
-    "Universal review checklist — code quality, readability, testability, security, contracts, Definition of Done"
-  ],
-  "capabilities": [
-    "code",
-    "review",
-    "checklist"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/code-review-checklist/agents/skill.yaml

@@ -1,23 +0,0 @@
-version: 1
-name: "code-review-checklist"
-display_name: "Universal Code Review Checklist"
-description: "Universal review checklist — code quality, readability, testability, security, contracts, Definition of Done."
-default_prompt: "Use $code-review-checklist when the task matches the \"Universal Code Review Checklist\" skill."
-triggers:
-  - "code-review-checklist"
-  - "code review checklist"
-  - "Universal Code Review Checklist"
-  - "Universal review checklist — code quality, readability, testability, security, contracts, Definition of Done"
-capabilities:
-  - "code"
-  - "review"
-  - "checklist"
-tools: []
-invocation:
-  explicit: true
-  implicit: true
-localization:
-  default_locale: "en"
-  available_locales:
-    - "ru"
-    - "en"

package/locales/en/.agents/skills/current-state-analysis/SKILL.md

@@ -1,141 +0,0 @@
----
-name: current-state-analysis
-description: Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency.
----
-
-# Skill: Current State Analysis
-
-How to audit a repository before making major architectural decisions or refactoring.
-
-**Sections:**
-1. [When to use](#1-when-to-use)
-2. [Workflow](#2-workflow)
-3. [Analysis Areas](#3-analysis-areas)
-4. [Output Template](#4-output)
-
----
-
-## 1. When to use
-
-The Architect or Senior Full Stack agent uses this skill:
-- **During Discovery:** When taking over an existing repository.
-- **Before major refactoring:** To understand the baseline.
-- **Before system design:** To identify constraints and existing patterns that shouldn't be duplicated.
-
----
-
-## 2. Workflow
-
-```
-1. Get the repository structure (find_by_name, ls)
-2. Identify the technology stack (package.json, go.mod, dockerfile)
-3. For each analysis area (Architecture, Data, UI, DX):
-   a. Sample 3-5 representative files
-   b. Look for consistency (e.g., are there 3 ways to fetch data?)
-   c. Identify red flags (hardcoded secrets, missing auth, god objects)
-4. Synthesize the findings into the Analysis Report
-5. Propose immediate remediation steps (if requested)
-```
-
----
-
-## 3. Analysis Areas
-
-### 3.1 Architecture & Structure
-
-Check how the code is organized.
-
-| What to look for | Tooling / Pattern | Good | Bad |
-|------------------|-------------------|------|-----|
-| **Module boundaries** | `find_by_name`, structure | By feature (`features/products`) or layer (`src/controllers`) | Flat `src/` with 50 files, or `misc/` folder |
-| **Data flow** | `grep "fetch("` or `grep "axios"` | Through explicit services/API clients | Directly from UI components |
-| **State management** | `package.json`, React Context | Zustand, RTK Query, or well-scoped Context | Prop drilling 5 levels deep, redundant global state |
-| **Routing** | React Router / Next.js app dir | Centralized, lazy loaded where needed | Scattered `<Route>` definitions, no 404 handling |
-
-### 3.2 Code Quality & Consistency
-
-Check if the team is writing code the same way.
-
-| What to look for | Tooling / Pattern | Good | Bad |
-|------------------|-------------------|------|-----|
-| **Linting/Formatting**| `package.json` (ESLint, Biome, Prettier) | Strict CI checks, `biome.json` | Missing, or lots of `eslint-disable` |
-| **Naming Conventions**| Sampling files | `camelCase` for vars, `PascalCase` for React | Mixed `snake_case` and `camelCase` in JS |
-| **Component Size** | File sizes | < 200 lines, focused | 1000+ line God Components |
-| **Testing** | `__tests__` or `*.test.ts` | High coverage on business logic | No tests, or only empty generated tests |
-
-### 3.3 Security & Resiliency
-
-Check for obvious vulnerabilities and fragility.
-
-| What to look for | Tooling / Pattern | Good | Bad |
-|------------------|-------------------|------|-----|
-| **Secrets** | `grep "API_KEY"` or `grep "password"` | Environment variables (`process.env`) | Hardcoded tokens in source code |
-| **Authentication** | Middleware/HOCs | Centralized auth check / protected routes | Ad-hoc checks, leaked sensitive data |
-| **Error Handling** | `try/catch`, Error Boundaries | Global error boundary, unified API error format | Unhandled promise rejections, blank screens |
-| **Dependencies** | `npm audit`, `package.json` | Up-to-date, minimal external deps | Known vulnerabilities, 5 different date libraries |
-
-### 3.4 UI & Performance
-
-Check how the frontend is built and how it performs.
-
-| What to look for | Tooling / Pattern | Good | Bad |
-|------------------|-------------------|------|-----|
-| **Styling Strategy** | CSS Modules, Tailwind, WDS | Consistent use of one strategy | Mixed inline styles, global CSS, and Tailwind |
-| **Rendering** | Over-fetching, hydration | Memoization where needed, optimized images | 10MB bundle, `useEffect` infinite loops |
-| **Accessibility (a11y)**| `aria-`, semantic HTML | `<button>`, native focus, correct contrast | `onClick` on `<div>` without keyboard support |
-
----
-
-## 4. Output Template
-
-```markdown
-# Current State Analysis: <Project/Module Name>
-
-**Date:** YYYY-MM-DD
-**Analyst:** <Agent Role>
-
-## 1. Executive Summary
-<2-3 sentences summarizing the overall health and major findings.>
-
-## 2. Tech Stack & Architecture
-- **Frontend:** React 18, Vite, Zustand
-- **Backend:** Node.js, Express (if monolithic repo)
-- **Styling:** CSS Modules
-- **Pattern:** Layered architecture (Controllers -> Services)
-
-## 3. Findings
-
-### 3.1 Architecture & Consistency
-- ✅ **Good:** Routing is centralized in `src/routes.tsx`.
-- ⚠️ **Warning:** Two different data fetching patterns found (raw `fetch` vs custom `apiClient`). Need to unify.
-- 🔴 **Red Flag:** `Dashboard.jsx` is 850 lines long and handles rendering, data fetching, and complex logic (God Object).
-
-### 3.2 Security & Error Handling
-- ✅ **Good:** Passwords are never sent to the client.
-- 🔴 **Red Flag:** Production API keys found hardcoded in `src/config/keys.js`. (Requires immediate rotation and .env extraction).
-- ⚠️ **Warning:** Missing global React Error Boundary. Unhandled exceptions crash the whole tree.
-
-### 3.3 UI & Code Quality
-- ✅ **Good:** ESLint is configured and running strictly.
-- ⚠️ **Warning:** Minimal unit test coverage (only 3 tests exist).
-
-## 4. Recommendations & Tech Debt
-
-**Immediate Remediation (P0):**
-1. Extract secrets from `src/config/keys.js` to `.env`.
-2. Refactor `Dashboard.jsx` into smaller pure components.
-
-**Short-term Tech Debt (P1):**
-1. Unify data fetching to use `apiClient` exclusively.
-2. Implement global Error Boundary.
-
-**Long-term Strategy (P2):**
-1. Introduce Vitest for unit testing critical services.
-```
-
----
-
-## See also
-- `$architecture-doc` — Use the analysis to propose the new architecture.
-- `$system-design-checklist` — To ensure no areas are missed during redesign.
-- `$security-review-baseline` — For deeper security audits.

package/locales/en/.agents/skills/current-state-analysis/agents/claude.json

@@ -1,18 +0,0 @@
-{
-  "name": "current-state-analysis",
-  "display_name": "Current State Analysis",
-  "description": "Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency.",
-  "default_prompt": "Use $current-state-analysis when the task matches the \"Current State Analysis\" skill.",
-  "triggers": [
-    "current-state-analysis",
-    "current state analysis",
-    "Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency"
-  ],
-  "capabilities": [
-    "current",
-    "state",
-    "analysis"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/current-state-analysis/agents/copilot.json

@@ -1,18 +0,0 @@
-{
-  "name": "current-state-analysis",
-  "display_name": "Current State Analysis",
-  "description": "Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency.",
-  "default_prompt": "Use $current-state-analysis when the task matches the \"Current State Analysis\" skill.",
-  "triggers": [
-    "current-state-analysis",
-    "current state analysis",
-    "Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency"
-  ],
-  "capabilities": [
-    "current",
-    "state",
-    "analysis"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/current-state-analysis/agents/gemini.json

@@ -1,18 +0,0 @@
-{
-  "name": "current-state-analysis",
-  "display_name": "Current State Analysis",
-  "description": "Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency.",
-  "default_prompt": "Use $current-state-analysis when the task matches the \"Current State Analysis\" skill.",
-  "triggers": [
-    "current-state-analysis",
-    "current state analysis",
-    "Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency"
-  ],
-  "capabilities": [
-    "current",
-    "state",
-    "analysis"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/current-state-analysis/agents/kimi.yaml

@@ -1,14 +0,0 @@
-name: "current-state-analysis"
-display_name: "Current State Analysis"
-description: "Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency."
-default_prompt: "Use $current-state-analysis when the task matches the \"Current State Analysis\" skill."
-triggers:
-  - "current-state-analysis"
-  - "current state analysis"
-  - "Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency"
-capabilities:
-  - "current"
-  - "state"
-  - "analysis"
-tools: []
-implicit_invocation: true

package/locales/en/.agents/skills/current-state-analysis/agents/openai.yaml

@@ -1,8 +0,0 @@
-interface:
-  display_name: "Current State Analysis"
-  short_description: "Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bot…"
-  default_prompt: "Use $current-state-analysis when the task matches the \"Current State Analysis\" skill."
-dependencies:
-  tools: []
-policy:
-  allow_implicit_invocation: true

package/locales/en/.agents/skills/current-state-analysis/agents/qwen.json

@@ -1,18 +0,0 @@
-{
-  "name": "current-state-analysis",
-  "display_name": "Current State Analysis",
-  "description": "Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency.",
-  "default_prompt": "Use $current-state-analysis when the task matches the \"Current State Analysis\" skill.",
-  "triggers": [
-    "current-state-analysis",
-    "current state analysis",
-    "Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency"
-  ],
-  "capabilities": [
-    "current",
-    "state",
-    "analysis"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/current-state-analysis/agents/skill.yaml

@@ -1,22 +0,0 @@
-version: 1
-name: "current-state-analysis"
-display_name: "Current State Analysis"
-description: "Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency."
-default_prompt: "Use $current-state-analysis when the task matches the \"Current State Analysis\" skill."
-triggers:
-  - "current-state-analysis"
-  - "current state analysis"
-  - "Analysis of the current repository architecture — conventions, patterns, tech debt, scaling bottlenecks, security risks, and consistency"
-capabilities:
-  - "current"
-  - "state"
-  - "analysis"
-tools: []
-invocation:
-  explicit: true
-  implicit: true
-localization:
-  default_locale: "en"
-  available_locales:
-    - "ru"
-    - "en"