blacksmith-testbox

Validate code changes against a real CI environment using the blacksmith testbox CLI.

1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/sheriax/drawink --skill blacksmith-testbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blacksmith-testbox
Source: https://github.com/sheriax/drawink/tree/main/.agents/skills/blacksmith-testbox
Command: npx skills add https://github.com/sheriax/drawink --skill blacksmith-testbox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a consistent and secure environment to run tests, builds, and migrations, ensuring code changes are validated against real CI conditions before committing.

Core Features & Use Cases

  • CI Environment Simulation: Executes commands within a pre-configured CI environment, including dependencies and services.
  • Secure Secret Management: Handles sensitive information and services required for testing.
  • Use Case: Before pushing a new feature, use this Skill to run all integration tests and database migrations to ensure they pass in an environment identical to production.

Quick Start

Use the blacksmith-testbox skill to run 'npm test' in the backend directory.

Frequently Asked Questions about blacksmith-testbox

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

FAQPage Schema
How do I validate code changes against a real CI environment before committing?

You can validate code changes by running tests, builds, and migrations against a real CI environment using the blacksmith testbox CLI. This simulates production CI conditions securely, executing commands within a pre-configured environment that includes necessary dependencies and services.

How does CI environment simulation handle secure secret management for integration tests?

CI environment simulation handles secure secret management by securely processing sensitive information and services required for testing. This ensures that secrets are managed safely while executing commands within the pre-configured CI environment during validation runs.

Do I need the blacksmith CLI installed and authenticated to run database migrations in a CI environment?

Yes, running database migrations in this CI environment requires the blacksmith CLI to be installed and authenticated. You must use either agent-triggered browser authentication or an API token to execute the validation commands securely.

Can I use this CI environment simulation to run npm test in a specific backend directory?

Yes, you can use this CI environment simulation to run npm test in a specific backend directory. The environment executes commands within a pre-configured CI setup, ensuring tests run under real CI conditions before pushing code.

What is the best way to ensure database migrations pass in an environment identical to production?

The best way to ensure database migrations pass in a production-identical environment is to run them through a real CI environment simulation. This validates code changes against actual CI conditions, securely handling required secrets and services before committing.

When should I not use a pre-configured CI environment for code validation?

You should not use a pre-configured CI environment for code validation if the blacksmith CLI cannot be installed or authenticated in your current setup. The simulation requires this CLI dependency to securely handle secrets and execute builds or tests.