Skill Claude CodeCodex
Integration test design principles for a connected end-to-end flow. Use when writing, reviewing, refactoring, or adding test cases under cicd/tests/ (the YAML flow and the runner). Enforces one self-contained, connected flow with no hardcoded or standalone tests. The principles are project-agnostic; the concrete…
Skill Claude CodeCodex
How to format text for TestLink fields. TestLink stores rich-text fields (summary, preconditions, step actions and expected results) as HTML, so field bodies must be written with HTML tags and escaped entities — not plain text or \n. Use whenever building or updating a TestLink test case or suite, and as the markup…
Skill Claude CodeCodex
Guidelines for writing or changing this project's MCP server code — adding or modifying TestLink tools.
Skill Claude CodeCodex
Reviews a TestLink change after the fact to confirm it achieved the user's goal — the right entities exist, fields are correct and well-formed, and the source document is faithfully represented. Use after testlink-sync or any manual create/update in TestLink, before calling the work done. The review gate paired with…
Skill Claude CodeCodex
Reads a source document — a spec, a GitHub issue, a markdown test-case file, a folder of them — and creates or updates the matching content in TestLink: requirements, test suites, test plans, builds, and test cases. Use when a QA engineer wants to import, sync, upload, or push content into TestLink from a document.…