skills.rest
loteiron
loteironCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

zeus-engineering

Implements coding tasks with baseline-aware verification of observed workspace checks.

Updated Sep 10, 2026
Search Tags:#git#testing#verification#coding#regression#baseline#delivery
One-click install
npx skills add https://github.com/loteiron/ZeusAgent --skill zeus-engineering-loteiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zeus-engineering
Source: https://github.com/loteiron/ZeusAgent/tree/main/skills/software-development/zeus-engineering
Command: npx skills add https://github.com/loteiron/ZeusAgent --skill zeus-engineering-loteiron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents delivery claims that are not backed by actual test, lint, and build results by preserving a baseline of existing failures and distinguishing repairs, persistent failures, and regressions. ## Core Features & Use Cases - Baseline Capture: Records observed check outcomes before editing so later results can be compared as fixed, regression, persistent_failure, unchanged, new, or incomparable. - Evidence-Gated Delivery: Uses zeus verify --status --json to confirm every required check is current and passing before marking work complete. - Use Case: When fixing a reported bug, reproduce the failure with a failing test, implement the fix, rerun the targeted and neighboring checks, then compare against the captured baseline to prove no regressions were introduced. ## Quick Start Ask the agent to run the zeus-engineering workflow on your coding task, for example by invoking /zeus-engineering followed by a description of the change you want implemented and verified.

Frequently Asked Questions about zeus-engineering

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

FAQPage Schema
How do I verify code changes against a baseline before delivery?▼

Capture a baseline with zeus verify --capture-baseline --json before editing, then after changes run zeus verify --status --json and compare outcomes. Results are classified as fixed, regression, persistent_failure, unchanged, new, or incomparable.

How to detect existing project checks without running them?▼

Run zeus verify --detect-only --json to inspect the existing recipe and its commands without executing anything. Detection and status commands never execute a project recipe, so you can read the prescribed test runner first.

What does exit code 1 from zeus verify --status mean?▼

Exit code 1 means the evidence is incomplete, failed, stale, or unavailable. Exit 0 only occurs when observed checks are current and passing, while exit 2 indicates invalid arguments.

Can a passing targeted test override a failed full test suite?▼

No. Each exact command, working directory, and scope has a separate result, so a targeted pass cannot erase a failed broad suite. Every required stale check must be rerun after the final source edit.

What are the limitations of workspace verification evidence?▼

Source receipts exclude ignored dependencies, remote services, and runtime environment changes, which must be verified separately. Non-Git, remote, or unsupported workspaces cannot receive local source proof, and external editors can invalidate results.

Related Skills

Explore More Software Engineering Skills→
Base-AnaliticaBase-Analitica

test-driven-development

Enforces red-green-refactor test-driven development workflow before writing production code.

Official
Intermediate
crisnahinecrisnahine
9

chameleon-pr-review

Automate Pull Request code reviews against repository conventions and principles.

Community
Advanced
TechDufusTechDufus
173

debugger

Diagnose failures and identify root causes through structured hypothesis testing.

Community
Advanced
AlexenderSokolovAlexenderSokolov
2

ds-lite-coordinate

Plans and collects approval-gated delegation of up to three bounded research subtasks.

Community
Advanced