← 全部工具

AdvancingTitans/agent-engineering-toolkit

热度 65 更新于 AI 与 Agent

Evidence-first engineering guardrails for coding agents: audit instructions, review change scope, record execution proof, and explain repository evolution.

githubauto-collected

安装

暂未验证可直接使用的安装命令,请查看项目官方文档或 Release。

Agent Engineering Toolkit

简体中文 · Start here · Full product reference

Your coding agent says tests passed. AET proves which code was actually tested.

Proof-carrying workflows for coding agents. AET binds test runs, changed files, artifacts, and agent claims into portable evidence, then tells you when that proof no longer applies.

uvx --from agent-engineering-toolkit aet demo stale-proof

Released in AET v1.18.0 and verified from the public PyPI package.

AET stale-proof demo

1. Test command executed                    PASS
2. Proof matches the tested source          EXACT_MATCH
3. Source changed without rerunning tests   RELEVANT_FILES_CHANGED

The test really passed, but that proof no longer applies to the current code.
Demo result: PASS

AET is not another coding agent. AET does not replace tests or CI. It does not turn missing evidence into PASS, and it does not auto-edit, auto-commit, push, merge, or release.

What the demo proves

The installed demo runs a real standard-library test in a temporary Git repository, records a Quick Proof against the exact fixture source, verifies EXACTMATCH, changes a declared relevant file without rerunning the test, and then reports RELEVANTFILESCHANGED.

That means:

  • the test really executed and passed;
  • the historical result remains a real fact;
  • the old proof no longer applies to the changed source;
  • the expected stale detection makes the demo itself pass.

It does not prove that every test passed, that an Agent's implementation is correct, or that a change should be merged. Git is required. Missing dependencies, unreadable fixtures, timeouts, and broken proof data fail closed as UNAVAILABLE, UNKNOWN, or a nonzero exit.

Four Quick Skills

| Question | Skill | CLI | | --- | --- | --- | | Are Agent instructions usable and verifiable? | /aet-check | aet quick check . | | Does this diff stay inside the approved task? | /aet-scope | aet quick scope . --base main --intent aet.intent.json | | Did this exact command run on these files? | /aet-proof | aet quick proof --output proof.json --relevant-path src/app.py -- python -m unittest | | Does an older proof still apply? | /aet-fresh | aet quick fresh --proof proof.json | | What should change, without editing yet? | /aet-plan | aet plan context ... |

The first four are bounded daily Quick surfaces. /aet-plan is a separate, read-only PROPOSED planning handoff; it never grants implementation or verification authority.

Real workflows

Stale proof