foxctl-dev

Inspect diffs, run tests, and check CI results with claim verification.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill foxctl-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foxctl-dev
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-pack/foxctl-dev
Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates uncertainty during development by helping you inspect changes, run the right checks, and quickly understand CI results before shipping.

Core Features & Use Cases

  • Change-focused verification: Inspect staged vs unstaged diffs and understand what actually changed.
  • Targeted test execution: Run the project’s test suite with configurable coverage, race detection, and verbosity for faster feedback loops.
  • CI status and PR triage: Check repository status in GitHub and leave PR comments to streamline remediation.
  • Chain-of-Verification (CoVe): Extract claims from drafts and validate them in parallel, including strict “gate” mode for Definition of Done evidence checks.

Quick Start

Run the verification loop for your current changes by asking the skill to inspect diffs, run tests, and then check CI status for the commit or branch you care about.

Frequently Asked Questions about foxctl-dev

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

FAQPage Schema
How do I verify code changes and run the right tests before merging a pull request?

To verify code changes before merging, inspect staged and unstaged diffs to identify changes, execute targeted tests with configurable coverage and race detection, and check CI results to build pre-merge confidence.

What is the best way to triage failing CI checks and PR comments for a GitHub repository?

Triage failing CI checks and PR comments by checking repository status in GitHub, analyzing CI check results, and leaving PR comments to streamline remediation and document debugging steps.

How does chain of verification validate technical claims during development?

Chain of verification (CoVe) validates technical claims by extracting statements from drafts and validating them in parallel, offering a strict gate mode for Definition of Done evidence checks.

Can I run test suites with race detection and configurable coverage for diff analysis?

Yes, you can run test suites with configurable coverage, race detection, and verbosity for faster feedback loops during diff analysis to validate development changes quickly.

Do I need a specific input format to trigger git status and diff analysis commands?

Yes, you need a JSON input envelope to trigger commands for git status, code diff analysis, test execution, CI checks, and PR comments during the verification loop.

What are the limitations of using automated diff verification for CI checks?

Automated diff verification requires structured JSON input envelopes for commands and focuses on GitHub metadata for PR triage, meaning it may not support platforms lacking compatible git status or CI check integrations.