Agentic tool updates
Choose the smallest local interface that fits your workflow. Provider-backed advice remains optional; deterministic tools continue to work without it.
SHAFT Pilot
- What it does
- Provides provider-neutral contracts and local orchestration through shaft-pilot-core.
- Why use it
- Keep optional model access behind SHAFT provider controls.
- Configure
- Add shaft-pilot-core only when an integration needs Pilot contracts.
- Use it
- Call the supported Pilot workflow from the linked guide.
IntelliJ Assistant
- What it does
- Provides project-scoped guidance and SHAFT tools inside the IntelliJ plugin.
- Why use it
- Ask for help and apply reviewed actions without leaving the IDE.
- Configure
- Install the plugin and complete its Assistant setup.
- Use it
- Open Assistant, choose a supported capability, and review every proposed change.
IntelliJ test run, debug, and watch
- What it does
- Runs, debugs, and watches focused SHAFT tests from the IDE tool window.
- Why use it
- Keep feedback beside the edited test and its evidence.
- Configure
- Open the SHAFT Tests tool window in a recognized project.
- Use it
- Select a test, choose run or debug, and inspect the watched result.
SHAFT Doctor
- What it does
- Analyzes allowlisted Allure evidence and failure traces locally.
- Why use it
- Triage failed runs from their artifacts without requiring a model provider.
- Configure
- Add shaft-doctor and point it at the failed run evidence.
- Use it
- Run Doctor, inspect its evidence-backed findings, then verify any fix.
SHAFT Heal
- What it does
- Proposes deterministic, explainable recovery for eligible changed web locators.
- Why use it
- Review a targeted locator replacement instead of guessing.
- Configure
- Add shaft-heal and use the documented healer workflow.
- Use it
- Inspect the candidate, accept only a stable locator, then rerun the test.
MCP, CLI, and agent skills
- What it does
- Exposes the same local SHAFT capabilities through MCP clients, one-shot CLI calls, and task-specific skills.
- Why use it
- Choose the integration surface that matches the coding environment.
- Configure
- Install only the MCP, CLI, or skills route the environment uses.
- Use it
- Invoke a documented tool, inspect its output, and keep project changes reviewable.
ChaosEngine harness
- What it does
- Installs a project-local agent workflow with verified host adapters and local tooling.
- Why use it
- Give supported agents one repeatable workspace process.
- Configure
- Run the project-local installer and its verification command.
- Use it
- Start the supported coding host from the configured repository.
Optional AI providers
- What it does
- Adds provider advice through opt-in adapters that remain disabled by default.
- Why use it
- Use model assistance only when project policy accepts the provider.
- Configure
- Select a documented provider and supply credentials through approved secure configuration.
- Use it
- Enable it for the intended workflow, then review provider output before applying changes.
Planning test coverage
- What it does
- Crawls same-origin content deterministically and drafts a Markdown test plan in specs/.
- Why use it
- Start coverage review from a repeatable crawl instead of an untracked prompt.
- Configure
- Connect SHAFT MCP and choose the documented planning tool for the target URL.
- Use it
- Review the generated plan, correct its scope, and keep only approved scenarios.
Trust-gated natural-language actions
- What it does
- Translates approved intent into GUI actions through a separate surface that is disabled by default.
- Why use it
- Opt into intent-based actions only where project trust controls allow them.
- Configure
- Enable the documented trust gate explicitly; leave it disabled elsewhere.
- Use it
- Submit a bounded action, review the resolved target, and verify the result.
Install only the tool route your environment uses:
MCP, CLI, IntelliJ, or agent skills
