audit-feedback-loop

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Scan the current repository and score its feedback loop maturity for AI-assisted development.

扫描当前代码仓库，为其AI辅助开发的反馈循环成熟度评分。

Instructions

操作说明

Analyze this repository and score its feedback loop maturity using the levels below. Check for each signal, then output a summary report.

分析此代码仓库，并使用以下等级为其反馈循环成熟度评分。检查每个信号，然后输出一份总结报告。

Maturity Levels

成熟度等级

Level 0 — Vibes No CI config, no linter rules, no CLAUDE.md. The AI agent is flying blind.

Level 1 — Guardrails Has CI + standard linters, but no custom rules. The agent gets basic feedback but can't learn project-specific conventions.

Level 2 — Architecture as Code Has custom lint rules, CLAUDE.md rules have enforcement annotations. The agent gets rich, project-specific feedback.

Level 3 — The Organism Has CI + custom rules + screenshot/visual tests + observability + scheduled agent tasks. The entire development loop is instrumented.

Level 0 — 凭感觉 无CI配置、无linter规则、无CLAUDE.md。AI Agent完全盲目工作。

Level 1 — 基础防护 具备CI + 标准linters，但无自定义规则。Agent可获得基础反馈，但无法学习项目特定规范。

Level 2 — 架构即代码 具备自定义lint规则，CLAUDE.md规则带有强制执行注解。Agent可获得丰富的、项目专属的反馈。

Level 3 — 有机闭环 具备CI + 自定义规则 + 截图/可视化测试 + 可观测性 + 定时Agent任务。整个开发循环已实现全面监控。

Signals to Check

需检查的信号

Scan the repository for the following and note which exist:

CI Configuration: Look for

.github/workflows/

.circleci/

Jenkinsfile

.gitlab-ci.yml

bitbucket-pipelines.yml

.travis.yml

, etc.

Linter Config (language-aware):

JS/TS:

eslint.config.*

.eslintrc*

biome.json

.prettierrc*

deno.json

Python:

pyproject.toml

(look for

[tool.ruff]

[tool.pylint]

[tool.flake8]

setup.cfg

.flake8

ruff.toml

Rust:
```
clippy.toml
```
,
```
.clippy.toml
```
,
```
rustfmt.toml
```
Go:
```
.golangci.yml
```
,
```
.golangci.yaml
```
Ruby:
```
.rubocop.yml
```
Java/Kotlin:
```
checkstyle.xml
```
,
```
pmd.xml
```
,
```
detekt.yml
```

Custom Lint Rules: Look for custom plugins, rule directories, or inline rule definitions in linter configs
- JS/TS:
```
eslint-plugin-*
```
  ,
```
eslint-rules/
```
  directories
- Python: custom Ruff/Pylint plugins, AST-based checks
- Rust: custom Clippy lints
- Go: custom analyzers
CLAUDE.md: Check if
```
CLAUDE.md
```
exists at the repo root
CLAUDE.md Enforcement: Check if using vigiles v2 specs (
```
CLAUDE.md.spec.ts
```
exists) or v1 annotations (
```
**Enforced by:**
```
in CLAUDE.md). v2 specs = higher maturity.
Type-Safe Specs: Check for
```
CLAUDE.md.spec.ts
```
or
```
*.spec.ts
```
files — indicates typed spec compilation via vigiles v2
Generated Types: Check for
```
.vigiles/generated.d.ts
```
— indicates linter rules are type-checked at authoring time
Screenshot/Visual Tests: Look for Playwright (
```
playwright.config.*
```
), Cypress (
```
cypress.config.*
```
), Chromatic, Percy, BackstopJS configs

Observability: Search for imports/usage of

@sentry/

dd-trace

@datadog/

newrelic

@opentelemetry/

sentry_sdk

structlog

tracing

(Rust),

opentelemetry

in source files

Scheduled Agent Tasks: Look for cron patterns in CI configs,
```
.github/workflows/
```
with
```
schedule:
```
triggers, or references to scheduled Claude Code tasks

扫描代码仓库，确认以下内容是否存在：

CI配置：查找

.github/workflows/

、

.circleci/

、

Jenkinsfile

、

.gitlab-ci.yml

、

bitbucket-pipelines.yml

、

.travis.yml

等文件。

Linter配置（语言相关）：

JS/TS：

eslint.config.*

、

.eslintrc*

、

biome.json

、

.prettierrc*

、

deno.json

Python：

pyproject.toml

（查找

[tool.ruff]

、

[tool.pylint]

、

[tool.flake8]

）、

setup.cfg

、

.flake8

、

ruff.toml

Rust：
```
clippy.toml
```
、
```
.clippy.toml
```
、
```
rustfmt.toml
```
Go：
```
.golangci.yml
```
、
```
.golangci.yaml
```
Ruby：
```
.rubocop.yml
```
Java/Kotlin：
```
checkstyle.xml
```
、
```
pmd.xml
```
、
```
detekt.yml
```

自定义Lint规则：查找自定义插件、规则目录或linter配置中的内联规则定义
- JS/TS：
```
eslint-plugin-*
```
  、
```
eslint-rules/
```
  目录
- Python：自定义Ruff/Pylint插件、基于AST的检查
- Rust：自定义Clippy lints
- Go：自定义分析器
CLAUDE.md：检查仓库根目录是否存在
```
CLAUDE.md
```
文件
CLAUDE.md强制执行：检查是否使用vigiles v2规范（存在
```
CLAUDE.md.spec.ts
```
）或v1注解（CLAUDE.md中包含
```
**Enforced by:**
```
）。v2规范代表更高成熟度。
类型安全规范：检查是否存在
```
CLAUDE.md.spec.ts
```
或
```
*.spec.ts
```
文件——表明通过vigiles v2实现了类型化规范编译
生成的类型：检查是否存在
```
.vigiles/generated.d.ts
```
——表明linter规则在编写阶段已进行类型检查
截图/可视化测试：查找Playwright（
```
playwright.config.*
```
）、Cypress（
```
cypress.config.*
```
）、Chromatic、Percy、BackstopJS的配置文件
可观测性：在源码文件中搜索
```
@sentry/
```
、
```
dd-trace
```
、
```
@datadog/
```
、
```
newrelic
```
、
```
@opentelemetry/
```
、
```
sentry_sdk
```
、
```
structlog
```
、
```
tracing
```
（Rust）、
```
opentelemetry
```
的导入/使用情况
定时Agent任务：在CI配置中查找cron模式、带有
```
schedule:
```
触发器的
```
.github/workflows/
```
，或与定时Claude Code任务相关的引用

Output Format

输出格式

undefined

undefined

Feedback Loop Audit

反馈循环审计报告

Repository: <repo name> Primary language(s): <detected languages> Score: Level X — <Name>

代码仓库: <仓库名称> 主要语言: <检测到的语言> 评分: Level X — <等级名称>

Signals Found

已发现的信号

CI Configuration: <details>
Custom Lint Rules: not found
CLAUDE.md: found, 5 enforced / 2 guidance / 1 missing ...

CI配置: <详情>
自定义Lint规则: 未找到
CLAUDE.md: 已找到，5项强制执行 / 2项指导 / 1项缺失 ...

Recommendations

建议

<Most impactful next step to level up>
<Second recommendation>
<Third recommendation>

<提升等级最有效的下一步措施>
<第二条建议>
<第三条建议>

How to Level Up

如何升级

<Specific, actionable advice for reaching the next maturity level>


Be specific about file paths and what you found. Give actionable recommendations tailored to the project's language and toolchain.

<针对项目语言和工具链的具体、可操作的建议>


请明确说明文件路径和发现的内容。根据项目的语言和工具链给出可操作的定制化建议。