shaft-skills

Plugin shaft-skills from marketplace shafthq in ShaftHQ/SHAFT_ENGINE. Commands read from the repo's manifest — today.

Skills (37)

• shaft-accessibility-testing

  Use when testing web or mobile accessibility for WCAG conformance, keyboard and focus behavior, semantics, errors, or user impact.

• shaft-android-apk-select

  Use when choosing a universal or ABI-split APK for a local emulator versus a real or cloud arm64 Android device.

• shaft-api-testing

  Use when implementing or repairing SHAFT.API tests for HTTP requests, authentication, payloads, schemas, responses, contracts, or service workflows.

• shaft-assertions

  Use when selecting or repairing SHAFT hard assertions, soft verifications, browser or element oracles, API checks, object checks, or failure messages.

• shaft-automated-test-authoring

  Use when implementing or repairing executable SHAFT Java tests for web, mobile, API, database, CLI, TestNG, JUnit, or Cucumber behavior.

• shaft-browserstack-native

  Use when configuring BrowserStack App Automate for SHAFT native Android or iOS: secrets keys, device pin, bs:// apps, Local, or triage.

• shaft-change-verification

  Use when edited SHAFT Java needs a reuse plan, preview diff, guardrail check, approved application, focused test, and evidence-backed verdict.

• shaft-cli

  Use when a SHAFT task needs a deterministic one-shot command, machine-readable output, offline discovery, or code generation from a persisted recording.

• shaft-database-testing

  Use when implementing or repairing SHAFT.DB checks for persisted state, queries, rows, transactions, cleanup, or database-backed integration behavior.

• shaft-defect-reporting

  Use when reporting a confirmed SHAFT product defect with severity, impact, environment, reproduction steps, expected and actual behavior, and evidence links.

• shaft-developer

  Use when starting any SHAFT testing task to select exactly one lifecycle, implementation, or tool specialist before doing the work.

• shaft-docs-hygiene

  Use when keeping SHAFT project docs lean: SoT trio, Done/In progress/Not started, hours math, adversarial review, or delete-guard.

• shaft-execution-reporting

  Use when reporting SHAFT execution to engineers with reconciled counts, coverage, environments, failures, defects, flakes, evidence, risks, and next actions.

• shaft-failure-analysis

  Use when investigating consistently failed SHAFT results through evidence, controlled reproduction, hypotheses, and root-cause ownership.

• shaft-flaky-test-analysis

  Use when SHAFT tests inconsistently pass or fail under equivalent conditions and need history, retry, timing, state, data, or environment analysis.

• shaft-fluent-api

  Use when composing or repairing SHAFT fluent browser, element, touch, assertion, verification, or report-message chains.

• shaft-guide-search

  Use when current official SHAFT syntax, configuration, migration, troubleshooting, or feature guidance must be found and cited before coding.

• shaft-ios-ipa-acceptance

  Use when gating an iOS IPA before BrowserStack or cloud upload: iphoneos, signing, arm64, thinning, or Info.plist checks.

• shaft-locator-design

  Use when identifying, ranking, repairing, or generating resilient SHAFT web or mobile locators from current DOM, ARIA, or accessibility-tree evidence.

• shaft-mcp

  Use when a SHAFT task needs structured tool calls, interactive exploration, or browser, mobile, driver, and capture state that persists across calls.

• shaft-mobile-actions

  Use when implementing SHAFT native or mobile-web sessions, context switches, taps, gestures, rotation, keyboard, or app lifecycle behavior.

• shaft-mobile-env

  Use when setting up or repairing a local SHAFT mobile env: JDK split, Appium pin, SDK/AVD, emulator memory, or doctor loop.

• shaft-mobile-retest-hygiene

  Use when triaging SHAFT mobile retest failures: map no-ops, picker probes, mixed bytecode, progress journals, or swipe fallback.

• shaft-nonfunctional-test-design

  Use when designing measurable risk-based tests for performance, security, reliability, recovery, compatibility, scalability, usability, or operations.

• shaft-page-objects

  Use when creating or refactoring reusable SHAFT page objects, component objects, locators, and user-intent methods without duplicating owners.

• shaft-recording-codegen

  Use when a persisted SHAFT web, Playwright, mobile, or API recording must become compilable, repository-aware Java code or insertion blocks.

• shaft-requirements-analysis

  Use when analyzing requirements for testability, acceptance criteria, traceability, contradictions, omissions, risks, assumptions, or coverage gaps.

• shaft-stakeholder-reporting

  Use when translating verified SHAFT coverage, outcomes, defects, trends, and residual risk into business quality or release decisions.

• shaft-test-case-design

  Use when designing reviewable test cases or scenarios with traceability, data, steps, expected results, techniques, priorities, and boundary coverage.

• shaft-test-completion

  Use when closing a SHAFT test cycle with exit-criteria evaluation, residual risk, archived testware, lessons, maintenance handover, or completion records.

• shaft-test-data-design

  Use when designing deterministic, private, isolated SHAFT test data with partitions, factories, seeding, uniqueness, cleanup, retention, or schema rules.

• shaft-test-environment

  Use when defining or troubleshooting SHAFT test environment readiness, parity, versions, configuration, dependencies, isolation, reset, or drift.

• shaft-test-execution

  Use when executing approved SHAFT tests with controlled scope, preflight checks, deterministic configuration, evidence, status reconciliation, and cleanup.

• shaft-test-monitoring

  Use when monitoring SHAFT test progress, coverage, quality gates, defects, risks, duration, flakiness, infrastructure health, or completion.

• shaft-test-planning

  Use when creating or revising a risk-based SHAFT test plan covering objectives, scope, approach, resources, estimates, schedule, criteria, and monitoring.

• shaft-test-recording

  Use when an approved live web, Playwright, native-mobile, mobile-web, Appium Inspector, or API flow must be captured with privacy-safe evidence.

• shaft-web-actions

  Use when implementing SHAFT WebDriver or Playwright navigation, browser state, element interaction, upload, drag-and-drop, window, cookie, or screenshot behavior.

Similar plugins