run-cases
openbooklet.com/s/run-casesopenbooklet.com/s/[email protected]GET /api/v1/skills/run-casesExecute approved test cases against a deployed DEV or staging environment, through the browser or an app on an Android device: refuse production and the local stack, recon the accounts and data, triage every case as automatable, semi-automatable, manual, or blocked, naming who clears each obstacle, agree the scope with the person before any case runs, run in at most three rounds, and write only the results it observed into a run record the QA lead approves and `atk:qa --bug` reads. Use when a cases file is approved, a non-production environment is deployed, and the team wants an agent to execute the automatable part instead of a tester. Triggers on: "run the test cases", "execute test cases", "run these cases on staging", "automate these test cases on DEV", "run test cases on the mobile app", "/atk:run-cases".
Extract, record, and enforce the coding conventions a team actually follows: branch and commit rules, naming, layering, error handling, test layout, review etiquette, and the tooling that enforces each rule. Also drafts the collaboration files the project lacks, `CONTRIBUTING.md`, the pull request template, and `CODEOWNERS`, writing only the ones the team picks. Use when a team has no written convention, when the written one no longer matches the code, or when reviews keep repeating the same comment. Triggers on: "convention", "coding standard", "coding rule", "style guide", "branch strategy", "commit convention", "our team rules", "CONTRIBUTING.md", "CODEOWNERS", "contribution guide", "set up a pull request template", "standards per language", "coding standard for each technology", "/atk:convention".
Does things with files.
Auto-indexed from lamngockhuong/aiteamkit
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.