testeiya 0.2.1 → 0.3.1-5.1

package/skills/testeiya/testomatio-docs/SKILL.md

@@ -1,102 +0,0 @@
----
-name: testomatio-docs
-description: The official Testomat.io product documentation, vendored as searchable markdown. Use whenever the user asks how Testomat.io works — test management, suites and tests, runs, reports and execution, manual and automated testing, TQL, tags/labels/custom fields, milestones, plans, branches, imports and exports, CI/issue-tracker/SSO integrations, reporter setup, users and permissions, plans and billing — or asks where something is in the Testomat.io interface, or uses a Testomat.io term you cannot define with certainty (rungroup, pipe, detached test, shared step, environment, merge strategy, living doc, bulk edit, artifact). Search the docs before answering; never answer a Testomat.io platform question from memory.
----
-
-# Testomat.io documentation
-
-The full product documentation of Testomat.io, vendored from
-[testomatio/docs](https://github.com/testomatio/docs) at build time. It is on disk — no network
-needed.
-
-## Layout
-
-- `INDEX.md` — every page as `` `<file>` — **Title** — <public URL> — description ``.
-- `docs/<file>` — the page itself, mirroring the paths in the index.
-- `docs.lock.json` — the source commit these pages were vendored from.
-
-Reach them through `skill://testomatio-docs/<path>` — it resolves to this skill's directory in
-`bash` and `read` alike.
-
-## How to search
-
-1. **Grep `INDEX.md` first** — titles and descriptions carry most feature keywords, and one hit
-   gives you the file, the public URL and a summary at once:
-
-   ```bash
-   grep -i '<term>' skill://testomatio-docs/INDEX.md
-   ```
-
-2. **Then grep the pages** when the index misses:
-
-   ```bash
-   grep -ril '<term>' skill://testomatio-docs/docs
-   ```
-
-   Try the user's wording *and* the product's (a user's "folder" is a **suite**, "ticket" is an
-   **issue**, "test case" may be a **test** or a **shared step**).
-
-3. **Read the matching page** — `read skill://testomatio-docs/docs/<file>` — before answering.
-   Follow links between pages when a page defers to another.
-
-Never answer from memory when the question is about the platform — the product changes, these
-files do not lie. If the docs genuinely do not cover it, say so plainly instead of guessing.
-
-## Testeiya is a client, not the web app
-
-Testeiya is a standalone client for the same Testomat.io backend the docs describe. Three
-consequences, and they matter for every answer you give from these pages:
-
-### 1. Every documented feature exists and works
-
-The docs describe the platform, and the user's project runs on that platform. Do not hedge with
-"if your plan supports it" or "this may not be available" — assume any documented capability is
-real. Know the full feature set: it is what the user is entitled to and what you can help them
-use.
-
-### 2. The interface in the docs is the **web app's**, not Testeiya's
-
-Screenshots, menus, tabs, buttons, "click the ⋮ next to the suite" — none of that describes
-Testeiya's own UI. Testeiya has a chat, a file tree and a markdown editor; it does not reproduce
-the web app's screens.
-
-So when an answer is about *where to click* or *what a screen looks like*:
-
-- Never instruct the user to find something inside Testeiya because the docs said so — the
-  control is not here and they will hunt for it.
-- Point them at their Testomat.io host instead, resolved in this order:
-  1. `baseUrl` in the workspace's `.testeiya/testeiya.json` (this is the project's real host —
-     self-hosted installs are not `app.testomat.io`),
-  2. the `TESTOMATIO_URL` environment variable,
-  3. `https://app.testomat.io` as the default.
-- Say it explicitly — "in the Testomat.io web app at `<host>`, open …" — so the user knows they
-  are switching tools.
-- Cite the public docs URL from `INDEX.md`, never the local file path or a `skill://` URI.
-
-### 3. Prefer doing the thing over describing where to click
-
-A large share of what the docs present as UI work you can perform on the user's behalf:
-
-- **Testomat.io MCP tools** — read and modify tests, suites, runs, testruns, plans, labels and
-  tags directly (`tests_*`, `suites_*`, `runs_*`, `testruns_*`, `plans_*`, `labels_*`, `tags_*`,
-  plus CRUD). See the `testomatio-mcp` skill.
-- **`check-tests` pull/push** — sync test cases between the project and local `*.test.md` files.
-  See the `check-tests` skill.
-
-Check what your tools actually cover before answering. Offer the action first and the manual
-web-app route second; fall back to "here is where it is in the web app" only when no tool reaches
-it (billing, SSO, project settings, plugin installs, and anything else purely administrative).
-
-## Unfamiliar terms
-
-If the user uses a Testomat.io term whose exact meaning you are not sure of, grep the docs before
-you reply. Guessing at product vocabulary produces confidently wrong answers — a *run group* is
-not a *plan*, a *label* is not a *tag*, and a *detached* test is not a *deleted* one.
-
-## Answer shape
-
-- Lead with the answer, then the steps or the tool call.
-- Link the public docs URL for anything the user may want to read in full.
-- When the answer involves the web app, name the host you are sending them to.
-- When a documented feature needs setup the workspace does not have yet (a reporter, a CI profile,
-  an integration), say what is missing rather than assuming it is configured.

package/skills/testeiya/testomatio-docs/docs/advanced/ai-powered-features/ai-agents.md

@@ -1,144 +0,0 @@
----
-title: AI-Agents
-description: Discover Testomat.io’s AI Agents — intelligent tools designed to automate test management tasks like identifying flaky tests, enhancing descriptions, and converting projects to BDD. Learn how these agents help optimize your test suites, improve traceability, and reduce manual effort across large-scale testing projects.
-type: article
-url: https://docs.testomat.io/advanced/ai-features/ai-agents
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io, AI Agents, AI-powered test management, flaky test detection, test description improvement, BDD conversion, automated test optimization, test lifecycle automation, Pulse integration, test cleanup, behavior-driven development, automated QA workflows, test labeling, requirement traceability, AI in software testing, test intelligence
----
-
-## AI-Agents
-
-Testomat.io introduces another AI-powered feature — **AI-Agents** — designed to automate and enhance key aspects of your test management workflow using machine learning and intelligent logic.
-
-- **Deep Analyze** - Deeply analyzes the project and provides a comprehensive overview of the running status and coverage of tests.
-- **Improve Test Descriptions** - Go through all tests with descriptions and improve their markdown formatting. This action won't change the content, only improves the formatting. Applied changes can be safely reverted in Pulse.
-- **Write Descriptions from Code** - Updates all automated tests which have no description by analyzing their code and writing descriptions.
-- **Mark Flaky Tests** - Adds "Flaky" label to all flaky tests detected by analytics. Update analytics settings to customize flaky detection.
-- **Mark Failed Tests** - Adds "Failed" label to all tests that failed all the time. Analytics will detect tests that failed for last month.
-- **Transform Project to BDD** - Creates a new project with all the tests converted to BDD Gherkin format.
-
-![AI Agents](./images/AI_agents.gif)
-
-:::note
-
-These powerful AI-features are available in the **Enterprise plan**.
-
-:::
-
-### 1. 🔎 Deep Analyze
-
-**'Deep Analyze'** is an intelligent AI-agent that performs a comprehensive audit of your testing project. It provides a clear overview of test execution, coverage, and identifies critical gaps that could block a release — ideal for QA leads, product managers, and teams preparing for production readiness.
-
-#### Key Capabilities
-
-- **Analyzes entire test suites** for execution status, stability, and coverage.
-- **Summarizes functional areas** by mapping tests to key modules or features.
-- **Identifies missing, never-executed, or placeholder tests**.
-- **Highlights critical gaps** in business logic, security, and performance testing.
-- **Assesses release readiness** based on test data from the last 14 days.
-- **Provides actionable recommendations** to close gaps and improve completeness.
-
-![Deep Analyze](./images/Deep_analyze.gif)
-
----
-
-### 2. 🍿 Mark Flaky Tests
-
-**'Mark Flaky Tests'** uses execution analytics to automatically detect flaky tests—those that intermittently pass or fail without code changes—and labels them accordingly. This improves visibility and helps teams isolate unstable tests.
-
-#### Key Capabilities
-
-- **Automatically labels flaky tests** based on execution patterns.
-- **Isolates unreliable tests** to reduce CI/CD noise and instability.
-- **Improves test reliability** by enabling targeted review.
-- **Streamlines triage** with a consistent "Flaky" label.
-- **Supports customization** through Analytics Settings for detection rules and thresholds.
-
-![Mark Flaky Tests](./images/Marked_Flaky.png)
-
----
-
-### 3. 🚩 Mark Failed Tests
-
-**'Mark Failed Tests'** identifies tests that have failed 100% of the time over the past month and labels them as "Failed." This helps surface persistent issues that could block releases or degrade pipeline reliability.
-
-#### Key Capabilities
-
-- **Labels tests as "Failed"** if they have a 100% failure rate over the past month.
-- **Highlights critical failures** that require immediate attention.
-- **Improves visibility** into long-standing issues across the suite.
-- **Enables targeted filtering** and prioritization through labeling.
-
-![Mark Failed Tests](./images/Failed_tests.png)
-
----
-
-### 4. 📝 Improve Test Descriptions
-
-**'Improve Test Descriptions'** automatically enhances the formatting and readability of test case descriptions using Markdown — without changing the original content. It ensures descriptions are structured, easy to scan, and consistent across the project.
-
-#### Key Capabilities
-
-- **Parses existing descriptions** to detect structure and intent.
-- **Applies clean Markdown formatting**, including bullet points, emphasis, and separation of steps/results.
-- **Preserves original meaning** while improving presentation.
-- **Standardizes phrasing** for clarity and consistency.
-- **Cleans up grammar and punctuation** for professional polish.
-- **Non-destructive edits** — all changes can be reverted via **Rollback** button in Pulse.
-
-![Improve Test Description](./images/Improve_test_description.png)
-
----
-
-### 5. 🧙‍♂️ Write Descriptions from Code
-
-**'Write Descriptions from Code'** generates human-readable test descriptions by analyzing the test logic directly from code. It helps teams understand test intent without diving into implementation — especially useful in large repositories or during onboarding.
-
-#### Key Capabilities
-
-- **Generates descriptions** for automated tests lacking documentation.
-- **Analyzes code logic** to produce accurate summaries.
-- **Reduces manual effort** in documenting test cases.
-- **Improves onboarding** and cross-functional understanding.
-- **Supports traceability** and project clarity.
-- **All changes are reversible** via Pulse.
-
-![Write Description from Code](./images/Write_description_from_code.gif)
-
----
-
-### 6. 🎁 Transform Project to BDD
-
-**'Transform Project to BDD'** automatically converts your existing test project into BDD format using Gherkin syntax. It rewrites each test into the Given/When/Then structure, creating a new project that follows behavior-driven development practices.
-
-#### Key Capabilities
-
-- **Analyzes existing test cases** and rewrites them in Gherkin format.
-- **Creates a new project** with the converted BDD test suite.
-- **Supports Given/When/Then syntax** for clarity and structure.
-- **Eliminates manual rewriting**, accelerating BDD adoption.
-- **Improves collaboration** with non-technical stakeholders.
-- **Standardizes test style** across teams and projects.
-
-![Transform Project to BDD](./images/Transform_Project_to_BDD.gif)
-
----
-
-### 7. 🐷 Auto Detach Automated Tests
-
-**'Auto Detach Automated Tests'** identifies automated tests that haven’t been executed in the last 45 days and marks them as "Detached." This helps keep your test suite clean, relevant, and easier to manage.
-
-#### Key Capabilities
-
-- **Scans execution history** to detect unexecuted tests.
-- **Automatically detaches inactive tests**, flagging them for review.
-- **Supports test suite optimization** by surfacing potentially obsolete tests.
-- **Reduces noise** in dashboards and analytics.
-- **Improves test lifecycle management** by highlighting stale cases.
-- **Non-destructive** — detached status can be reverted via Pulse.
-
-![Auto Detach Automated Tests](./images/Detached_automated_tests.png)