context-preflight

Verify repository branch, worktree, and ticket context before file-changing work.

4|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/vmobifystudio/app-dev-team --skill context-preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-preflight
Source: https://github.com/vmobifystudio/app-dev-team/tree/main/skills/context-preflight
Command: npx skills add https://github.com/vmobifystudio/app-dev-team --skill context-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents agents from making repository changes based on stale, incomplete, or conflicting context by verifying the branch, worktree, ticket, dependencies, required documents, and unresolved obligations first.

Core Features & Use Cases

  • Repository State Validation: Check branch identity, worktree status, dirty files, and repository context before any change-making operation.
  • Dependency and Documentation Checks: Confirm ticket readiness, dependency ancestors, architecture guidance, engineering principles, Git strategy, and recent decisions.
  • Safe Decision Gates: Stop when context cannot be evaluated, distinguish facts from assumptions, and identify the next safe action.
  • Use Case: Before implementing a ticket in a shared repository, run a preflight to detect an unsuitable branch, uncommitted work, missing dependencies, or unresolved requirements before editing files.

Quick Start

Ask the context-preflight skill to verify the current project context before implementing the assigned ticket and report whether work can safely proceed.

Frequently Asked Questions about context-preflight

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

FAQPage Schema
How do I validate my repository branch and worktree before making code changes?

Repository context validation checks branch identity, worktree status, and dirty files before allowing implementation work. It prevents agents from making changes based on stale, incomplete, or conflicting repository context.

Why should I check ticket dependencies and engineering documentation before implementing a feature?

Checking ticket dependencies and engineering documentation confirms ticket readiness and verifies dependency ancestors are resolved. This prevents editing files when required architecture guidance or project principles are missing.

How do I run a preflight check to detect uncommitted work in a shared repository?

Running a preflight check detects uncommitted work by evaluating worktree status and dirty files. It reports repository state, distinguishes facts from assumptions, and identifies the next safe action before editing.

Can I use repository context validation for migration and release tasks, or only for implementation?

Repository context validation applies to implementation, review, migration, release, and other file-changing work. It verifies branch identity, ticket dependencies, and required documents for any repository modification.

What happens when repository context cannot be evaluated during a preflight check?

When repository context cannot be evaluated, the preflight check triggers safe decision gates that stop the workflow. It distinguishes facts from assumptions and identifies the next safe action to resolve the issue.