{
  "markdown": "<div align=\"center\">\n\n<picture>\n  <source media=\"(prefers-color-scheme: dark)\" srcset=\"shaft-engine/src/main/resources/images/shaft_white.png\">\n  <img src=\"shaft-engine/src/main/resources/images/shaft_standard.png\" alt=\"SHAFT S logo\" width=\"260\">\n</picture>\n\n# SHAFT\n\n**Reliable Java test automation, from first intent to production-grade evidence.**\n\nOne strong, maintainable framework for Web, Mobile, API, CLI, Database, and\nnative testing—with synchronized actions, configuration-first execution,\nreadable assertions, and unified reports.\n\n[![Maven Central](https://img.shields.io/maven-central/v/io.github.shafthq/shaft-engine?style=for-the-badge&logo=apachemaven)](https://central.sonatype.com/artifact/io.github.shafthq/shaft-engine)\n[![Build](https://img.shields.io/github/actions/workflow/status/ShaftHQ/SHAFT_ENGINE/pr-gate.yml?branch=main&style=for-the-badge&label=build)](https://github.com/ShaftHQ/SHAFT_ENGINE/actions/workflows/pr-gate.yml)\n[![Stars](https://img.shields.io/github/stars/ShaftHQ/SHAFT_ENGINE?style=for-the-badge&logo=github)](https://github.com/ShaftHQ/SHAFT_ENGINE)\n[![User guide](https://img.shields.io/badge/user_guide-live-006ec0?style=for-the-badge)](https://shafthq.github.io/)\n\n**[Generate your first project](https://shafthq.github.io/)** ·\n**[Explore the user guide](https://shafthq.github.io/)** ·\n**[Star SHAFT on GitHub ⭐](https://github.com/ShaftHQ/SHAFT_ENGINE)**\n\n</div>\n\nSHAFT removes the repeated plumbing around drivers, waits, assertions,\nconfiguration, test data, screenshots, logs, and Allure evidence. Its modular\nMaven reactor keeps the core lean and lets teams add advanced tooling only when\nthey need it.\n\n## From zero to useful evidence\n\n1. [Open the SHAFT landing page](https://shafthq.github.io/) and generate a\n   ready-to-run Maven project.\n2. Extract it and run:\n\n   ```shell\n   mvn test\n   ```\n\n3. Inspect the sample result, screenshots, logs, and Allure evidence.\n\nThe generated project uses the canonical Maven coordinate\n**io.github.shafthq:shaft-engine** and gives you a repeatable baseline\nfor local runs and CI.\n\n## One orchestration layer, every execution surface\n\nTest intent and configuration enter SHAFT's orchestration layer, fan out across\nthe required execution surfaces, and return through one unified evidence flow.\n\n```mermaid\nflowchart LR\n    accTitle: SHAFT execution and evidence workflow\n    accDescr: Test intent and configuration enter SHAFT orchestration, run across Web, Mobile, API, and Native execution surfaces, and produce unified evidence.\n    I[Test intent] --> S[SHAFT orchestration]\n    C[Configuration] --> S\n    S --> W[Web]\n    S --> M[Mobile]\n    S --> A[API]\n    S --> N[Native, CLI, and Database]\n    W --> E[Unified evidence]\n    M --> E\n    A --> E\n    N --> E\n```\n\n| Engineering need | What SHAFT provides |\n|---|---|\n| Stable UI automation | Managed Selenium and Appium drivers, synchronized actions, locator builders, screenshots, and accessibility evidence. |\n| End-to-end coverage | REST, GraphQL, Database, CLI, and native desktop actions in the same test flow. |\n| Trustworthy verdicts | Hard and soft assertions, structured logs, attachments, failure context, and Allure reports. |\n| Scalable execution | Configuration-first local, Grid, BrowserStack, LambdaTest, TestNG, JUnit, and Cucumber runs. |\n| Maintainable architecture | A focused engine, BOM-aligned optional modules, public extension points, and reusable test assets. |\n| Assisted workflows | Capture, Doctor, deterministic Heal, MCP/CLI tools, provider adapters, and an IntelliJ IDEA plugin. |\n\n## Built for long-lived automation suites\n\n- **Strong defaults, explicit control.** Sensible behavior gets teams moving;\n  configuration keeps environments and CI reproducible.\n- **Modular by design.** Start with `shaft-engine`, then adopt visual, video,\n  cloud, native, or agentic modules without rebuilding the test architecture.\n- **Evidence is part of execution.** Logs, screenshots, attachments, and\n  reports share one lifecycle instead of becoming after-the-fact glue.\n- **Open and inspectable.** SHAFT is MIT licensed, built in public, and guarded\n  by its [pull-request gate](.github/workflows/pr-gate.yml),\n  [security policy](SECURITY.md), and published\n  [release history](https://github.com/ShaftHQ/SHAFT_ENGINE/releases).\n\n## Agent-ready, source-grounded\n\nSHAFT ships 30 first-party skills for planning, authoring, running, diagnosing,\nand reporting tests. Start with `$shaft-developer`; it routes the immediate job\nto one focused specialist. Exact MCP names and CLI syntax are generated from\nsource in [`shaft-mcp-tools.md`](shaft-skills/references/shaft-mcp-tools.md) and\n[`shaft-cli-commands.md`](shaft-skills/references/shaft-cli-commands.md).\n\n## Join the project\n\n- Found a bug or have an idea? [Open an issue](https://github.com/ShaftHQ/SHAFT_ENGINE/issues).\n- Want to contribute? Read [CONTRIBUTING.md](CONTRIBUTING.md) and our\n  [Code of Conduct](CODE_OF_CONDUCT.md).\n- Found a vulnerability? Follow [SECURITY.md](SECURITY.md) and report it\n  privately.\n- Does SHAFT help your team? [Star the repository](https://github.com/ShaftHQ/SHAFT_ENGINE)\n  so more automation engineers can find it.\n\nBrowserStack, LambdaTest, Applitools, and JetBrains have provided tooling or\nopen-source program support. This is support for the project, not a claim of\nfinancial sponsorship, customer status, or endorsement.\n\nSHAFT is free and MIT licensed. You can support ongoing maintenance,\ndocumentation, and public infrastructure through\n[GitHub Sponsors](https://github.com/sponsors/MohabMohie).\n\nMIT licensed — see [LICENSE](LICENSE).\n",
  "bytes": 5610,
  "sha": "81a68aa6ec88eaa6834abe270c88af479afe99b41e515d6795b973f6fa03261e",
  "repo_slug": "shafthq/shaft_engine",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_shafthq_shaft_mcp_27981dfb/readme"
}