Agent skill · software engineering · aiskillstore
engineering-loop
Drive an authorized repository change through a verified local loop: baseline, reproduce, implement, test, review, and report evidence. Use for end-to-end features or fixes that should continue autonomously until observable acceptance criteria pass; do not use for explanation-only, review-only, or production operations.
Why this skill is useful
Provides a structured, domain-specific workflow for managing repository changes that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Engineering Loop Own the change from a verified starting point to a reviewed result. Use one agent and this skill alone unless a specialist changes a material decision. Establish the baseline 1. Read applicable AGENTS.md files and repository documentation. 2. Record the requested behavior, constraints, and observable done conditions. 3. Inspect the branch and working tree; preserve unrelated user-owned changes. 4. Identify repository-native validation and run the smallest safe baseline that separates pre-existing failures from task regressions. For a long, cross-stack, or high-risk change, use the templates and failure rules in references/loop-contract.md. When a defect is intermittent, performance-related, difficult to reproduce, or resists the first evidence-driven pass, use references/hard-debugging.md. Run the loop 1. Reproduce the defect, or capture the current behavior for a feature. 2. Choose the smallest coherent change and the evidence that will prove it. 3. Add a failing regression test first when practical. 4. Implement one bounded change and run the narrowest relevant check. 5. Classify failures as product, test, environment, or assumption failures; fix the cause and rerun the affected check. 6. Run repository-required broader checks after focused checks pass. 7. Inspect the complete diff and perform a fresh findings-first review. 8. Fix consequential findings and rerun checks affected by those fixes. Keep a compact ledger of confirmed facts, changed files, commands, outcomes, and the next decision. Return concise diagnostics instead of full logs. Stop conditions If the same command fails twice for the same reason, stop retrying and re-check the environment, target, permissions, and underlying assumption. Stop and report a blocker when progress requires missing authority, secrets, unavailable infrastructure, destructive action, or a product decision. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/engineering-loop