kestrel-mcp-health

To verify project health, you can run a baseline health check to assess repository cleanliness and deployment readiness. This requires a properly configured Python environment and access to the project's verification scripts to identify code health and baseline consistency issues.

To safely rollback changes when issues are detected, you can trigger a safety rollback routine to revert uncommitted changes or problematic commits. This restores the repository to a stable baseline state across the MCP workflow.

Yes, you need a properly configured Python environment to run Kestrel MCP health checks. Additionally, you must have access to the project's verification scripts to successfully execute the baseline consistency checks and rollback procedures.

The best way to automate project verification is by using command routing with phrases like full_verify and rollback. This guides automated workflows to trigger baseline health checks and safely revert changes when issues are detected.

Repository health verification fails after recent commits due to detected baseline consistency issues or code health degradation. You can execute a safety rollback to revert the problematic commits and restore the repository to a stable state.