Loading...
Loading...
Found 53 Skills
File a GitHub issue for local integration test failures. TRIGGERS: file test bug, report test failure, create bug for test, integration test failed, test failure issue, junit failure
This skill should be used when a QA engineer wants to test or verify a completed task, run through acceptance criteria, check Gherkin scenarios against the implementation, record pass/fail results, or sign off on a ticket before merge. Triggers on phrases like "verify task
Comprehensive QA testing orchestrator. Use when user says 'test', 'qa', 'check site', 'find bugs', 'helpmetest', provides a URL to test, or wants complete testing coverage from discovery through bug reporting. Discovers ALL pages, enumerates ALL features, tests comprehensively, reports exact metrics.
Report a bug or feature request in One Horizon. Use when asked "I found a bug", "track this issue", "log this defect", "log this feature request", "capture this product ask", or "track this enhancement". Requires One Horizon MCP.
Expert in quality assurance and testing. Responsible for bug detection, edge case validation, test planning, and automated test creation to ensure software reliability.
Issue creation workflow for Agent Teams Lite following the issue-first enforcement system. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.
Report a bug in the compound-engineering plugin
Systematic exploratory QA testing of web applications — find bugs, capture evidence, and generate structured reports
Phase 1 of the Issue Workflow - Translate the user's problem into a reproducible, traceable {slug}-report.md through conversation. The AI only asks "what you saw, how to reproduce it, what should happen" here, and does not guess the root cause for the user (that's Phase 2's responsibility). This phase is also the only official decision point for determining whether to take the fast track or the standard path: first read the relevant code based on the user's description, and if the root cause can be identified at a glance and the changes required are minor, directly inform the user to take the fast track. Trigger scenarios: The user says "file an issue", "log this bug", "I found a problem". This is the starting point of the issue workflow with no pre-requisites.
Translate ideas, feature requests, or vague concepts into specific, actionable dev briefs. Use this skill whenever the user has an idea they want to build, a feature to spec out, a bug to file, a project to scope, or needs to convert a half-formed idea into a clear implementation brief. Triggers on I want to add, we should build, can we make, what is the plan for, how do we implement, dev brief, feature spec, PRD, user story, acceptance criteria, scope this, prioritize. Also triggers when the user has a list of things they want to build and needs help converting them into well-formed tasks.
Submit GitHub issues, feature requests, bug reports, product suggestions, and feedback to the ZenMux repository (ZenMux/zenmux-doc). Use this skill whenever the user wants to: report a bug, request a feature, suggest a product improvement, give feedback, request support for a new model or provider, report a documentation issue, or share their experience. Trigger on phrases like: "submit issue", "file a bug", "feature request", "report a problem", "I have an idea", "提交issue", "提反馈", "功能建议", "报告bug", "产品建议", "提个需求", "新增模型", "新增供应商", "文档问题", "我想提个建议", "提交建议". If the user is describing a ZenMux problem or product idea and would benefit from submitting it formally, proactively offer to help them create an issue.
Report a bug in the compound-engineering plugin