preflight

Verify GitHub issue state, blockers, and project board transitions before implementation.

2|Updated Feb 23, 2026

Search Tags:#automation #workflow #devops #github #issue tracking #preflight

Ready to run

npx skills add https://github.com/evanharmon1/harmon-devkit --skill preflight-evanharmon1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: preflight
Source: https://github.com/evanharmon1/harmon-devkit/tree/main/ai/skills/universal/preflight
Command: npx skills add https://github.com/evanharmon1/harmon-devkit --skill preflight-evanharmon1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, task, and includes assets (resource) components.

What problem does it solve?

This skill eliminates the uncertainty of starting a new task by performing a comprehensive sanity check on GitHub issues, ensuring you have the correct context and preventing conflicts before you begin implementation.

Core Features & Use Cases

Automated Sanity Checks: Verifies issue status, checks for existing PRs, and identifies stale references or template-managed conflicts.
Safe Issue Claiming: Coordinates issue assignment, labeling, and project board status updates with built-in safety prompts and conflict detection.
Use Case: Before starting work on a complex bug, run this skill to confirm the issue is still open, check if other developers are already working on it, and automatically move the card to In Progress once you are ready to start.

Quick Start

Invoke the preflight skill by typing /preflight followed by the issue number to analyze the target issue and prepare your workspace.

Frequently Asked Questions about preflight

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

FAQPage Schema

How do I validate a GitHub issue before starting development to avoid conflicts?▼

To validate a GitHub issue before starting development, you can run an automated preflight sanity check that verifies the issue status, checks for existing pull requests, and identifies stale references or template-managed conflicts.

What is the safest way to claim an unassigned GitHub issue and move it to In Progress?▼

The safest way to claim an unassigned GitHub issue is to use an automated workflow that coordinates issue assignment, labeling, and project board transitions with built-in safety prompts and conflict detection before mutating issue metadata.

Do I need git and gh installed to automate issue tracking and project board transitions?▼

Yes, you need git, gh, and task installed to automate issue tracking and project board transitions, because the preflight process requires synchronizing your local git repositories with the remote GitHub issue tracker.

Can I check if another developer is already working on a GitHub issue?▼

You can check if another developer is already working on a GitHub issue by running an automated sanity check that verifies the issue state, identifies blockers, and detects existing pull requests associated with the issue.

What are the limitations of using automated sanity checks for GitHub issue validation?▼

A limitation of automated sanity checks for GitHub issue validation is that while repository status and template provenance are read-only validated, any mutation of issue metadata requires explicit user confirmation before execution.