mission-airlock

Run tests, lint, and type checks before task completion.

3|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/thebrownproject/space-agents --skill mission-airlock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mission-airlock
Source: https://github.com/thebrownproject/space-agents/tree/main/skills/mission-airlock
Command: npx skills add https://github.com/thebrownproject/space-agents --skill mission-airlock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the quality gate for software tasks by running tests, linting, and type checks to ensure code quality before handoff or deployment.

Core Features & Use Cases

  • Run tests across the detected project type and report results.
  • Execute linting and type checks to catch syntax, style, and type issues early.
  • Integrate with blocking workflows to halt progress on failures and create actionable tickets or CAPCOM-style blockers.
  • Use cases: After implementing a feature, trigger the airlock to validate health and prevent regressions before release.

Quick Start

Run the airlock gate on your feature branch to verify tests and lint pass before merging.

Frequently Asked Questions about mission-airlock

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

FAQPage Schema
How do I automate code quality checks before merging a feature branch?

Automating code quality checks before merging involves running a quality gate that executes tests, lint, and type checks across your project. This validates feature health and prevents regressions before release.

What is a quality gate in CI/CD and how does it enforce code quality?

A quality gate in CI/CD is a validation step that enforces code quality by running tests, linting, and type checking. It halts progress on failures and creates actionable tickets to block flawed merges.

Can I use automated lint and type checking across multi-language software projects?

Yes, you can use automated lint and type checking across multi-language software projects. The quality gate applies a consistent validation step across repositories, detecting the project type to run appropriate checks.

How do I stop a pull request from merging if tests or linting fail?

To stop a pull request from merging when tests or linting fail, integrate a blocking workflow that halts progress on failures. This creates actionable tickets or blockers, preventing handoff until validation passes.

When should I run type checking and linting during feature completion workflows?

You should run type checking and linting during feature completion workflows after implementing a feature. Triggering the airlock gate at this stage catches syntax, style, and type issues early before handoff or deployment.