个人作者

MhmdElGazzar

更新于 2026-10-26

Skills
17
仓库
1
职业覆盖
0
场景覆盖
0
Stars
★ 21

MhmdElGazzar 的 Skills 17

MhmdElGazzar
MhmdElGazzar/agentex

ui-check

Execute ui-check: steps in test specs — compare the live page currently open in the browser under test against a declared design baseline: a Figma frame (identifier only; file + token configured once per project) or a screenshot image, in exact mode (every visible detail) or reference mode (only enumerated details can fail). Triggers on spec steps starting with "ui-check:", or requests like "check this page against the design", "compare with the Figma frame", "does the screen match the mockup". Baselines are resolved by the bundled fetch_baseline.js runner — an unresolvable baseline is BLOCKED, never improvised; the comparison verdict itself is agent-vision judgment.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

tracker-ops

Ad-hoc work-item operations on the configured tracker — Azure DevOps or Jira Cloud — behind one approval per write batch. Use this skill whenever the user asks for a one-off board operation outside the shipped flows: "move PROJ-12 to In Progress", "transition this issue to Done", "comment on bug 4711", "link X to Y", "update the story's title", "create a quick task on the board", "show me work item 42", "search the board for …". Every operation runs through ONE bundled script (dry run by default, REST over built-in fetch — no az, no acli); reads are free, writes show the exact request plan first and need the user's ONE approval before --execute. Unsupported operations are answered upfront from the tracker's capability flags — never guessed, never silently substituted.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

test-execution

Run test specs against an application and report defects, routing each step to its driver (browser via playwright-cli, API calls, database checks, knowledge-base questions, UI design checks). Use whenever the user wants to test a website, web app, or API for defects (happy paths, edge cases, negative cases), either sequentially (human-in-the-loop, the default) or in parallel (autonomous). Produces per-scenario evidence plus a consolidated defect report. Read this before starting any test run.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

test-design

Designs test cases for User Stories on the configured tracker — Azure DevOps or Jira Cloud: analyze a story's acceptance criteria into test conditions, map them to test case titles, create the test artifacts (ADO Test Cases with structured steps, or the Jira issue type the user chooses — Jira has no native Test Case type) and link them to the parent story, behind ONE consolidated approval. Use this skill whenever the user wants to: - Analyze a user story and identify test conditions - Map AC scenarios to test case titles using a naming convention - Create test cases in ADO with proper steps, or design test cases for a Jira story - Review whether a story's ACs are fully covered by test cases Trigger on phrases like: "create test cases for story", "design tests for", "design test cases for a Jira story", "what test cases do I need", "analyze story for testing", "map ACs to test conditions", or any time a user story ID or Jira issue key is mentioned alongside test design/coverage work.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

task-estimation

Creates QA testing tasks with estimation on the configured tracker's User Stories — Azure DevOps or Jira Cloud. Reads the sprint, analyzes each story, then creates all [Testing] tasks (ADO Tasks or Jira sub-tasks) behind ONE consolidated approval, through bundled REST scripts (no Azure CLI, no acli). Use this skill whenever the user wants to: - Add QA tasks to sprint stories in Azure DevOps or Jira - Estimate testing hours for user stories - Create [Testing] tasks on ADO work items or [Testing] sub-tasks on Jira issues - Plan QA effort for a sprint - Break down stories into testing tasks with hours Trigger on phrases like: "create tasks for stories", "add QA tasks", "estimate sprint", "estimate the Jira sprint", "create testing tasks", "create tasks for Jira sprint stories", "add sub-tasks to Jira stories", "plan QA for sprint", "add tasks to stories", or any mention of sprint stories + estimation + testing.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

swagger-import

Generate an API catalog + suite of test cases (integration/api_test_suites/<service>/) from a Swagger 2.0 or OpenAPI 3.x JSON document. Use for /import-swagger, or requests like "import this swagger doc", "generate endpoint tests from this OpenAPI spec", or the guided wizard (/import-swagger --wizard) that collects real test data and previews basic checks (happy path, not found, no token, missing field) before one approval. Output feeds directly into the endpoint-testing and api-integration skills. This skill generates config and sends no API request of its own; any run, including the wizard's "Approve and run now", goes through endpoint-testing's runner.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

optimize-login

Pay a web application's login cost once per session instead of once per test — drive the login live, reduce it to the smallest script that works, save the browser session, and reload that session into a fresh browser to continue. Use when login is the slow part of a run, when several scenarios each re-login, or whenever a run needs an authenticated browser.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

mobile-testing

Test a native mobile app (Android/iOS) by driving it through Appium. Use whenever the user wants to test a mobile app for defects — happy paths, edge cases, and negative cases — either sequentially (human-in-the-loop, the default) or in parallel (autonomous, one session per available device/emulator). Produces per-scenario screenshots and logs plus a consolidated defect report. Read this before starting any mobile testing run.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

extent-report

Produce a standalone, self-contained extent-report.html — a dark-themed interactive dashboard (verdict banner, donut chart, per-status stat cards, expandable test-case cards with step-by-step detail). Use at the end of any playwright-cli test execution (one test case or a full parallel/sequential batch) once final scenario results are known, alongside report.md.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

endpoint-testing

Run a standalone API test pass over the project's cataloged endpoints ("api-tests"), independent of any browser test spec. Use for /test-endpoints, or requests like "run the API tests", "test all endpoints". Also opens the local API suite editor (/test-endpoints --edit) to review, fix and re-run cases, one suite or one case at a time. Use before editing any *_suite.json by hand, and whenever asked to enable, un-skip or remove "skip" lines from write cases (POST/PUT/PATCH/DELETE). Distinct from api-integration's `api:` step (a single cataloged call made mid-browser-test) — this skill runs the whole set of cases in one pass and returns a consolidated report. Execution is catalog+suite-only: only cases defined in integration/api_test_suites/**/*_suite.json, referencing entries defined in the sibling *_api.json catalog, ever run.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

define-flow

Define a test flow by doing it: an agent-led session that builds a spec step by step in a live browser — the agent proposes each step, executes it immediately, and the user asserts the real outcome before the next step is defined. Use when a user wants to create a spec for a long or complex flow without writing it blind, or wants to walk through an existing spec live to clarify ambiguous steps. Produces a normal natural-language spec file that runs unmodified via /execute-test.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

db-integration

Execute user-defined database queries during test runs, from the project's integration/ catalog (SQL Server via sqlcmd). Use whenever a test step needs a DB check: verify a row was created/updated by a UI action, check column values, or seed test data. Triggers on spec steps starting with "db:", or requests like "check the database", "verify the row", "query the table". The agent executes ONLY queries the user has defined in integration/*_db.json — it never composes its own SQL.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

bug-report-azure

After a completed test/regression run where one or more defects were found, file them as tracker Bugs on the configured tracker — Azure DevOps or Jira Cloud ("file these as Jira bugs" works the same) — following a configurable bug template, through bundled Node scripts that talk to the tracker REST API directly (no Azure CLI, no acli needed). Product/team-agnostic: org/site, project, area path, template, assignees, and test plan resolve from config, never hardcoded. ONE gate per filing: all reads and validation run first with zero board writes, then a single consolidated screen (validated fields + the exact write plan) and one approval before anything is written. Severity/priority recommended from the run's findings, screenshots validated in two passes, writes fail closed with an exact per-write ledger — the board never silently differs from what the user confirmed.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

browser-driver

The browser driver for test-execution runs. It drives a real browser through playwright-cli for unprefixed (prose) spec steps and covers isolated sessions, screenshot and console evidence, login modes, and the failure signatures that decide retry versus defect. Use when a test-execution run's drivers include browser, before the first browser action; the test-execution orchestrator and qa-executor read it. Not a standalone entry point.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

azure-integration

Interact with Azure resources from a QA/test run via the Azure CLI (`az`) — login/auth, discovery, and reading App Service, Storage, Key Vault, and AKS resources. Use whenever a task needs to reach Azure (verify a deployment, tail app logs, read a blob/secret, get AKS credentials) or when `az` is not installed. Read the reference before the first `az` command.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

ask-kb

Ask a project's knowledge base a natural-language question during a test run, via the KB Ask API, and read the answer as advisory context. Triggers on spec steps starting with "kb:", or requests like "ask the KB", "what does the knowledge base say", "how does <flow> work". Explicit only — the agent never calls the KB on its own initiative. Answers inform testing/navigation but are NEVER used as PASS/FAIL evidence.

★ 21
MhmdElGazzar
MhmdElGazzar/agentex

api-integration

Execute user-defined API calls during test runs, from the project's integration/ catalog. Use whenever a test step needs an HTTP call: verify via API that a UI action persisted, check an endpoint's response, or seed test data through a service. Triggers on spec steps starting with "api:", or requests like "verify via API", "call the endpoint", "check the response". The agent executes ONLY requests the user has defined in a *_api.json catalog (searched recursively under integration/) — it never composes its own HTTP requests.

★ 21