GitHub CLI Search Test Suite FAQs

Question 1

Does this skill invoke itself automatically?

Accepted Answer

No. To manage costs and performance, this is a 'Slash Command Only' skill. It is designed to ignore general mentions of testing and will only activate when you explicitly use the `/test-gh-skills` command or a direct instruction to run all tests.

Question 2

What does the GitHub CLI Search Test Suite skill do?

Accepted Answer

This skill executes a specialized Python orchestrator that runs 80 parallelized tests across six categories to validate GitHub CLI search commands. It ensures syntax accuracy, handles edge cases like platform-specific quoting, and provides a comprehensive assessment of production readiness.

Question 3

What kind of reporting does the test suite provide?

Accepted Answer

The suite generates hierarchical reports at four levels: a Master Report for high-level summaries, Group Reports for category-specific results, Individual Test Reports for debugging, and Reviewer Notes for AI-driven insights and recommendations.

Question 4

How does this skill improve my developer workflow?

Accepted Answer

It automates the tedious process of manual verification by running tests in parallel, reducing execution time from 8 minutes to under 3. It also includes a test-reviewer agent that performs automatic root cause analysis on failures, saving you hours of debugging.

Question 5

When should I use this skill?

Accepted Answer

You should use this skill specifically when you need to verify the reliability of GitHub CLI search capabilities. Because it is resource-intensive, it should only be triggered via the `/test-gh-skills` slash command or an explicit request to 'run the full test suite'.

GitHub CLI Search Test Suite

GitHub CLI Search Test Suite

主な機能

ユースケース

主な機能

ユースケース