inspequte-rule-no-go-resume

Resume static analysis rule implementations marked "No-Go" in GitHub Actions by importing plan, spec, and implementation artifacts from a source Pull Request.

8|2|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/KengoTODA/inspequte --skill inspequte-rule-no-go-resume
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inspequte-rule-no-go-resume
Source: https://github.com/KengoTODA/inspequte/tree/main/.codex/skills/inspequte-rule-no-go-resume
Command: npx skills add https://github.com/KengoTODA/inspequte --skill inspequte-rule-no-go-resume

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps developers resume work on static analysis rules that were previously marked as "No-Go" in CI pipelines, ensuring progress and completion of rule development.

Core Features & Use Cases

  • Resumes Failed Rule Implementations: Automatically imports necessary artifacts from a source Pull Request for rules that failed CI checks.
  • Completes Missing Work: Identifies and addresses gaps in implementation and testing based on the "No-Go" reason.
  • Updates Documentation: Records the implementation status and remediation actions in a history file.
  • Use Case: A developer's rule implementation failed CI with a "No-Go" status. This Skill can be used to re-open the work, import the original plan and spec, fix the identified issues, and update the status, allowing the CI to pass on the next attempt.

Quick Start

Use the inspequte-rule-no-go-resume skill to resume the rule implementation from the provided source PR URL.

Frequently Asked Questions about inspequte-rule-no-go-resume

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

FAQPage Schema
How do I resume a static analysis rule implementation that failed CI with a No-Go status?

To resume a static analysis rule implementation marked as No-Go, this Skill imports the plan, spec, and implementation artifacts from the source Pull Request. It then completes missing implementation and test coverage based on the No-Go reason to prepare the rule for a passing CI retry.

What is the best way to fix incomplete test coverage for a static analysis rule rejected by GitHub Actions?

The best way to fix incomplete test coverage for a rejected static analysis rule is to use this Skill to import artifacts from the source PR. It identifies and addresses testing gaps based on the documented No-Go reason to ensure the implementation is complete.

How does importing a source PR help complete stalled static analysis rule development?

Importing a source PR helps complete stalled static analysis rule development by retrieving the original plan and spec artifacts. This Skill uses those artifacts to identify implementation gaps and resolve the specific issues that caused the CI pipeline to fail.

Can I automatically update the no-go history reference file after fixing a failed rule implementation?

Yes, you can automatically update the no-go history reference file after fixing a failed rule implementation. This Skill records the updated implementation status and remediation notes in the history file as part of the resume process.

Do I need a specific source PR URL to restart a No-Go static analysis rule?

Yes, you need a source PR URL to restart a No-Go static analysis rule. The Skill requires this URL to import the necessary plan, spec, and implementation artifacts needed to address the CI failure reason and complete the work.