smoke-test

Run eight post-session health checks on git status, imports, tests, and files.

1|Updated Jan 26, 2026

Search Tags:#build #session-management #quality-assurance #health-check #tests #git-status

Ready to run

npx skills add https://github.com/manastalukdar/ai-devstudio --skill smoke-test-manastalukdar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/manastalukdar/ai-devstudio/tree/main/skills/smoke-test
Command: npx skills add https://github.com/manastalukdar/ai-devstudio --skill smoke-test-manastalukdar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run 8 post-session-start health checks to verify the project is in a working state — git clean, no broken imports, tests pass, key files present, and agent memory intact.

Core Features & Use Cases

Git status verification, merge-conflict detection, installer sanity checks, and structure validation to prevent mid-work interruptions.
Ensures essential files and skill directories are present and consistent across environments.

Quick Start

Run the eight health checks after session start to confirm readiness.

Frequently Asked Questions about smoke-test

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

FAQPage Schema

How do I run post-session health checks to verify project readiness?▼

Run post-session health checks to verify project readiness by executing deterministic shell commands that test git status, import integrity, key files, and memory state. The process outputs a concise pass/fail summary detailing specific failures.

What is a post-session health check for a development repository?▼

A post-session health check is an automated verification process that confirms a development repository is in a working state. It validates git cleanliness, import integrity, passing tests, key files, and memory state to prevent mid-work interruptions.

When do I need to run post-session health checks?▼

You need to run post-session health checks immediately after a session starts or following major changes to a development repository. This timing ensures you detect issues like merge conflicts or broken imports before continuing work.

Does the session health check detect broken imports and merge conflicts?▼

Yes, the session health check detects broken imports and merge conflicts. It runs eight automated checks covering git status verification, installer sanity checks, structure validation, and memory state to ensure project consistency across environments.

Why does my project readiness check fail after major changes?▼

Project readiness checks fail after major changes when the automated shell commands detect uncommitted git status, broken import integrity, failing tests, missing key files, or inconsistent agent memory state. The summary provides specific details on the failure.