skills.rest
Mossaka
MossakaCOMMUNITY
Explore all skills by this author →
Website𝕏@jiaxiao_zhouGitHub

smoke-test-pr

Apply a smoke label to gh-aw PRs and analyze workflow logs for true success.

Updated Jan 14, 2026
Search Tags:#automation#github-actions#pull-request#log-analysis#smoke-tests#mcp-connectivity#workflow-monitoring
One-click install
npx skills add https://github.com/Mossaka/skills --skill smoke-test-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-test-pr
Source: https://github.com/Mossaka/skills/tree/main/smoke-test-pr
Command: npx skills add https://github.com/Mossaka/skills --skill smoke-test-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Smoke tests on gh-aw PRs ensure changes don't break core workflows by applying a dedicated "smoke" label and validating workflow execution through log analysis, rather than relying on green statuses alone.

Core Features & Use Cases

  • Label-triggered testing: Apply and manage the "smoke" label on a PR to start the smoke verification workflow.
  • Workflow monitoring: Wait for the smoke-related GitHub Actions to start and complete, including targeted workflows like smoke-copilot, smoke-claude, smoke-codex, or any workflow containing "smoke" in its name.
  • Log analysis: Fetch and inspect logs to detect MCP connection failures, agent execution errors, firewall/network issues, and silent failures.
  • Reporting: Produce a comprehensive result summary including workflow statuses, true results, issues found, MCP status, agent behavior, and firewall observations.

Quick Start

Invoke this skill by running /smoke-test-pr <PR URL or number> to start smoke tests on the specified pull request.

Frequently Asked Questions about smoke-test-pr

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

FAQPage Schema
How do I verify a pull request smoke test beyond just checking for a green status?▼

To verify a pull request smoke test beyond a green status, you can trigger a label-based workflow and analyze the GitHub Actions logs to detect silent failures, agent execution errors, and MCP connection issues.

How do I trigger smoke tests on a GitHub pull request using a label?▼

You can trigger smoke tests by applying a dedicated "smoke" label to a pull request, which initiates targeted GitHub Actions workflows such as smoke-copilot, smoke-claude, or smoke-codex for validation.

What issues can GitHub Actions log analysis detect during a PR smoke test?▼

Log analysis during a PR smoke test can detect MCP server connectivity failures, agent execution errors, firewall or network issues, and silent workflow failures that a standard green status might hide.

Do I need any external dependencies to monitor GitHub Actions workflows for smoke tests?▼

No external dependencies are required; the skill manages label application, workflow monitoring, log extraction, and comprehensive result reporting autonomously within the GitHub Actions environment.

Why do my GitHub Actions workflow logs show a green status but the pull request still has MCP connectivity issues?▼

A green status can mask MCP connectivity issues because standard workflows may not fail visibly; analyzing the workflow logs extracts true results and identifies silent failures, firewall blocks, and agent errors.

Can I monitor specific agent workflows like smoke-copilot or smoke-claude during a pull request review?▼

Yes, you can monitor specific agent workflows like smoke-copilot, smoke-claude, or smoke-codex by waiting for any GitHub Actions workflow containing "smoke" in its name to start and complete during the PR review.

Related Skills

Explore More Software Engineering Skills→
matthewdeavesmatthewdeaves

setup-machine

Register a new Classic Mac in the MCP server and verify FTP connectivity.

Community
Intermediate
MossakaMossaka

debug-workflow

Diagnose GitHub Actions workflow failures by aggregating logs and MCP gateway status.

Community
Intermediate
N4M3ZN4M3Z
3

GitHub

Manage GitHub repositories, releases, pull requests, and Actions via gh CLI.

Community
Advanced
magnus919magnus919
40

woodpecker-ci

Operate and troubleshoot Woodpecker CI deployments, pipelines, and incidents.

Community
Advanced