skills.rest
thiagobutignon
thiagobutignonCOMMUNITY
Explore all skills by this author →
GitHub

dogfooding

Validate CLI commands in a live terminal against help text and contracts.

Updated Aug 27, 2026
Search Tags:#testing#cli#verification#command line#contract testing#dogfooding
One-click install
npx skills add https://github.com/thiagobutignon/nooa-the-pragmatic --skill dogfooding
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dogfooding
Source: https://github.com/thiagobutignon/nooa-the-pragmatic/tree/main/.agent/skills/dogfooding
Command: npx skills add https://github.com/thiagobutignon/nooa-the-pragmatic --skill dogfooding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that command-line interface (CLI) tools function correctly in real-world scenarios, preventing bugs and inconsistencies from reaching users.

Core Features & Use Cases

  • Manual Command Execution: Run commands in a live terminal to test their behavior.
  • Help Text Verification: Ensure that command descriptions and flag information are accurate and up-to-date.
  • Contract Satisfaction: Validate exit codes, output formats, and error handling for reliable integration.
  • Use Case: After adding a new flag to a CLI command, use this Skill to run the command with the new flag, check its help text, and confirm it produces the expected output and exit code.

Quick Start

Run the 'dogfooding' skill to verify the 'commit' command works as expected.

Frequently Asked Questions about dogfooding

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

FAQPage Schema
How do I verify CLI behavior and contracts after implementing a new feature?▼

To verify CLI behavior and contracts, you must manually execute commands in a live terminal, test edge cases, review help text, validate exit codes, and run the full test suite to ensure real-world functionality.

What is command-line interface contract testing and when do I need it?▼

Command-line interface contract testing validates that exit codes, output formats, and error handling meet expected specifications. You need it to prevent bugs and inconsistencies from reaching users in real-world scenarios.

How do I check CLI help text consistency for command-line tools?▼

Checking CLI help text consistency involves reviewing command descriptions and flag information in a live terminal environment to ensure they are accurate and up-to-date before completing the feature implementation.

Does manual command execution catch edge cases that automated tests miss?▼

Manual command execution in a live terminal catches real-world edge cases by validating actual behavior against expected outputs and exit codes, complementing automated test suites for thorough CLI verification.

What's the best way to validate exit codes and error handling for a new CLI flag?▼

The best way to validate exit codes and error handling is to run the updated command with the new flag in a live terminal, confirm it produces expected output, and execute the full test suite.

Related Skills

Explore More Software Engineering Skills→
posit-devposit-dev
132

r-btw-cli

Access R documentation, CRAN metadata, and development tasks from the command line.

Official
Intermediate
rsmdtrsmdt
381

cicd-patterns

Design CI/CD pipelines for GitHub Actions and GitLab CI with deployment strategies.

Community
Advanced
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate
Arsia-MonsArsia-Mons
4

using-silencer-cli

Automate Silencer menus, state capture, and gameplay validation via CLI.

Official
Intermediate