skills.rest
mindcockpit-ai
mindcockpit-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

smoke-test

Run automated smoke tests on web endpoints and create GitHub issues for failures.

11|1|Updated Feb 9, 2026
Search Tags:#automation#bug-tracking#endpoint-testing#web-app#github-issues#smoke-test#error-detection
One-click install
npx skills add https://github.com/mindcockpit-ai/cognitive-core --skill smoke-test-mindcockpit-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/mindcockpit-ai/cognitive-core/tree/main/core/skills/smoke-test
Command: npx skills add https://github.com/mindcockpit-ai/cognitive-core --skill smoke-test-mindcockpit-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the verification of web application endpoints to detect runtime errors early, reducing manual debugging and ensuring reliable deployments by integrating with GitHub for issue management.

Core Features & Use Cases

  • Endpoint Testing: Executes happy-path smoke tests using a configured command to check HTTP status and server logs for failures.
  • Automated Issue Creation: Scans results, deduplicates against existing issues, and creates GitHub tickets for new failures with detailed templates.
  • Reporting and Fixing: Generates markdown reports of test outcomes and supports re-testing to cross-reference and close resolved issues.
  • Use Case: In a development team building a React application, invoke this Skill daily to test all pages, catch JavaScript-induced errors like database exceptions, and automatically populate the project board with actionable bugs.

Quick Start

Invoke the smoke-test skill with run to execute tests on your endpoints and create GitHub issues for any detected failures.

Frequently Asked Questions about smoke-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate endpoint testing and create GitHub issues for failures?▼

Automate endpoint testing by running configured HTTP smoke tests against web endpoints, validating JSON output, and automatically generating deduplicated GitHub issues for detected server log errors. It scans test results and populates your project board with actionable bug tickets.

Can I run smoke tests on my React or Angular web application endpoints?▼

Yes, you can run smoke tests on React, Angular, or Node web applications using headless browser execution. The tests verify HTTP responses and check server logs to catch JavaScript-induced runtime errors like database exceptions across your endpoints.

How do I automatically track and resolve bug reports from web endpoint smoke tests?▼

Track bug reports by scanning smoke test results and deduplicating them against existing GitHub issues to create new tickets with detailed templates. You can generate markdown reports and trigger re-testing to cross-reference resolved endpoints and automatically close issues.

Do I need GitHub CLI and jq installed to automate endpoint testing and issue management?▼

Yes, you need both the GitHub CLI (gh) and jq installed. The GitHub CLI manages issue creation and resolution, while jq processes and validates the JSON output from your config-driven endpoint tests to detect server log errors accurately.

What is the best way to detect server log errors during web application endpoint testing?▼

The best way is executing config-driven happy-path smoke tests that verify HTTP status codes and scan server logs for runtime failures. This headless browser execution detects JavaScript-induced database exceptions and automatically creates GitHub tickets for new failures.

Why are my automated smoke tests not creating GitHub issues for detected endpoint failures?▼

Tests may not create issues if the detected failures are deduplicated against existing open GitHub tickets. The system scans results to prevent duplicate issue creation, so previously reported endpoint errors will not generate new bug tickets until the original issue is closed.

Related Skills

Explore More Software Engineering Skills→
indykishindykish
2

e2e-qa-playwright

Automate end-to-end QA for web applications using Playwright CLI.

Community
Intermediate
Jst-Well-DanJst-Well-Dan
8

test-fixing

Group failing tests by error type and module, then fix and verify them.

Community
Advanced
pmcdowallpmcdowall

github-issues

Create, organize, and resolve GitHub issues via CLI or REST API.

Community
Intermediate
congiuluccongiuluc

logging-angular

Capture and ship structured Angular client-side logs to a backend endpoint.

Community
Advanced