当前位置：首页 > news >正文

出行平台前端的 AI 质量门禁：提交前自动审查与合并条件的设计

news 2026/7/23 12:42:33

出行平台前端的 AI 质量门禁：提交前自动审查与合并条件的设计

一、质量门禁的必要性

出行平台前端代码的合并频率高、参与人数多。一次地图组件的改动，可能牵扯路线渲染、定位追踪、订单状态三个模块。如果仅靠人工 Review，合并排队时长会超出可接受范围，且漏检率随提交量线性上升。

AI 质量门禁的核心价值：在git push与merge之间建立一道自动化检查屏障。它不替代人工 Review，而是把低风险的格式、类型、依赖问题提前拦截，让 Reviewer 聚焦于业务逻辑与架构决策。

二、门禁架构设计

门禁分为两层：本地 Pre-commit 层和 CI 远程层。本地层侧重速度，300ms 内完成；远程层侧重深度，3min 内给出评分。

2.1 Pre-commit 层

本地层使用lint-staged+ 自定义脚本。检查项包括：ESLint 规则、类型推断、导入排序、未引用变量。AI 在此层仅做轻量推理——基于本地缓存的规则模型，对变更文件做增量分析。

// pre-commit-ai-check.ts — 本地AI轻量检查入口 import { spawn } from "child_process"; import { readFileSync } from "fs"; interface CheckResult { file: string; score: number; // 0-100，低于阈值则拦截 issues: string[]; // 具体问题描述 } const SCORE_THRESHOLD = 60; async function runLocalAICheck(stagedFiles: string[]): Promise<CheckResult[]> { const results: CheckResult[] = []; for (const file of stagedFiles) { // 跳过非代码文件 if (!/\.(ts|tsx|vue|js|jsx)$/.test(file)) { results.push({ file, score: 100, issues: [] }); continue; } try { const content = readFileSync(file, "utf-8"); // 调用本地规则模型进行增量推理 const score = await incrementalScore(content); const issues = await extractIssues(content); results.push({ file, score, issues }); } catch (err) { // 读取失败时降级为通过，避免阻塞提交 console.warn(`[门禁] 文件 ${file} 分析失败，降级通过: ${(err as Error).message}`); results.push({ file, score: 100, issues: [] }); } } return results; } // 增量评分：基于AST变更范围计算 async function incrementalScore(content: string): Promise<number> { // 仅对变更行做规则匹配，避免全文件扫描 const lines = content.split("\n"); let penalty = 0; for (const line of lines) { if (/console\.(log|warn|debug)/.test(line)) penalty += 5; if (/TODO|FIXME|HACK/.test(line)) penalty += 3; if (/any/.test(line) && !/\/\*.*any.*\*\//.test(line)) penalty += 8; } return Math.max(0, 100 - penalty); } async function extractIssues(content: string): Promise<string[]> { const issues: string[] = []; const lines = content.split("\n"); lines.forEach((line, idx) => { if (/console\.(log|warn|debug)/.test(line)) { issues.push(`行${idx + 1}: 生产代码不应包含 console 调用`); } if (/TODO|FIXME/.test(line)) { issues.push(`行${idx + 1}: 存在未完成的临时标记`); } }); return issues; } // 主流程：检查所有暂存文件 async function main(): Promise<void> { const stagedFiles = await getStagedFiles(); const results = await runLocalAICheck(stagedFiles); const blocked = results.filter((r) => r.score < SCORE_THRESHOLD); if (blocked.length > 0) { console.error("[门禁拦截] 以下文件未通过本地检查:"); blocked.forEach((r) => { console.error(` ${r.file} (评分: ${r.score})`); r.issues.forEach((i) => console.error(` - ${i}`)); }); process.exit(1); } console.log("[门禁通过] 所有文件评分均达到阈值"); } async function getStagedFiles(): Promise<string[]> { return new Promise((resolve, reject) => { const git = spawn("git", ["diff", "--cached", "--name-only"]); const output: string[] = []; git.stdout.on("data", (d) => output.push(d.toString())); git.stderr.on("data", (d) => console.error(d.toString())); git.on("close", (code) => { if (code !== 0) reject(new Error("git diff 执行失败")); else resolve(output.join("").split("\n").filter(Boolean)); }); }); } main().catch((err) => { console.error(`[门禁异常] ${(err as Error).message}`); process.exit(1); });

2.2 CI 远程层

远程层在 CI Pipeline 中运行，调用大模型做深度分析。审查维度包括：类型安全覆盖率、依赖引入合理性、潜在性能退化、业务逻辑一致性。

# ci-ai-gate.yml — CI层AI质量门禁配置 name: AI Quality Gate on: pull_request: types: [opened, synchronize] jobs: ai-review: runs-on: ubuntu-latest timeout-minutes: 5 steps: - uses: actions/checkout@v4 with: fetch-depth: 0 # 获取完整历史，便于上下文分析 - uses: actions/setup-node@v4 with: node-version: 20 - name: 安装依赖 run: npm ci - name: AI 深度审查 env: AI_MODEL_ENDPOINT: ${{ secrets.AI_MODEL_ENDPOINT }} AI_MODEL_TOKEN: ${{ secrets.AI_MODEL_TOKEN }} run: node scripts/ci-ai-review.mjs - name: 质量评分判定 run: node scripts/evaluate-score.mjs

三、合并条件的设计

合并条件是门禁的核心输出。它定义了"什么评分可以自动合并，什么评分需要人工介入"。

3.1 评分维度与权重

// score-model.ts — 评分维度与权重定义 interface ScoreDimension { name: string; weight: number; // 占总评分的权重 scorer: (ctx: ReviewContext) => Promise<number>; } interface ReviewContext { changedFiles: ChangedFile[]; branch: string; baseBranch: string; commitMessages: string[]; authorHistory: AuthorStats; } const dimensions: ScoreDimension[] = [ { name: "类型安全", weight: 0.25, scorer: async (ctx) => { // 检查变更文件中 TypeScript 严格模式的覆盖度 const tsFiles = ctx.changedFiles.filter((f) => f.ext === "ts" || f.ext === "tsx"); if (tsFiles.length === 0) return 80; // 无TS文件时给基础分 let total = 0; for (const f of tsFiles) { const anyCount = countAnyUsage(f.content); const strictCoverage = Math.max(0, 100 - anyCount * 10); total += strictCoverage; } return total / tsFiles.length; }, }, { name: "依赖合理性", weight: 0.20, scorer: async (ctx) => { // 检查新增依赖是否在项目白名单内 const newImports = extractNewImports(ctx.changedFiles); const whitelist = await loadDependencyWhitelist(); const violationRatio = newImports.filter((i) => !whitelist.includes(i)).length / Math.max(1, newImports.length); return Math.max(0, 100 - violationRatio * 100); }, }, { name: "性能影响", weight: 0.20, scorer: async (ctx) => { // 检查是否引入大型包或高开销操作 const bundleImpact = await estimateBundleImpact(ctx.changedFiles); return Math.max(0, 100 - bundleImpact); }, }, { name: "业务一致性", weight: 0.15, scorer: async (ctx) => { // AI分析变更是否符合当前业务语义 const analysis = await aiSemanticAnalysis(ctx); return analysis.consistencyScore; }, }, { name: "代码格式", weight: 0.10, scorer: async (ctx) => { // ESLint与Prettier规则的遵守率 const lintResult = await runLintCheck(ctx.changedFiles); return lintResult.passRate; }, }, { name: "提交规范", weight: 0.10, scorer: async (ctx) => { // Commit Message是否符合Conventional Commits const valid = ctx.commitMessages.filter((m) => isValidCommitMsg(m)).length; return (valid / Math.max(1, ctx.commitMessages.length)) * 100; }, }, ]; // 计算综合评分 async function computeGateScore(ctx: ReviewContext): Promise<number> { let total = 0; for (const dim of dimensions) { const score = await dim.scorer(ctx); total += score * dim.weight; } return Math.round(total); }

3.2 合并策略矩阵

// merge-policy.ts — 合并策略判定 interface MergeDecision { action: "auto_merge" | "auto_approve" | "block_review" | "block_fix"; reason: string; requiredReviewers?: string[]; fixSuggestions?: string[]; } function decideMergePolicy(score: number, riskFlags: string[]): MergeDecision { // 有高风险标记时，无论评分多少都需要人工介入 if (riskFlags.includes("security") || riskFlags.includes("breaking-change")) { return { action: "block_review", reason: "存在安全或破坏性变更标记，必须人工审查", requiredReviewers: ["security-team", "architect-team"], }; } if (score >= 85) { return { action: "auto_merge", reason: "评分优秀，自动合并" }; } if (score >= 70) { return { action: "auto_approve", reason: "评分合格，自动批准但可被Review" }; } if (score >= 50) { return { action: "block_review", reason: "评分偏低，需指定Reviewer审查", requiredReviewers: selectReviewers(riskFlags), }; } return { action: "block_fix", reason: "评分不合格，请修改后重新提交", fixSuggestions: generateFixSuggestions(score), }; } function selectReviewers(flags: string[]): string[] { const map: Record<string, string[]> = { performance: ["perf-team"], dependency: ["dep-reviewer"], type: ["type-guard"], logic: ["business-reviewer"], }; return flags.flatMap((f) => map[f] ?? ["default-reviewer"]); } function generateFixSuggestions(score: number): string[] { const suggestions: string[] = []; if (score < 30) suggestions.push("建议参照项目代码规范重写变更部分"); if (score < 50) suggestions.push("请检查类型标注完整度与依赖引入合理性"); suggestions.push("运行 npm run lint:fix 修复格式问题后重新提交"); return suggestions; }

四、出行场景的特殊适配

出行平台前端有独特的质量关注点，需要在通用门禁基础上做领域适配。

4.1 地图组件专项检查

地图组件是出行平台的核心，其变更需要额外审查：渲染帧率是否退化、定位精度是否受影响、离线缓存策略是否一致。

// map-specific-gate.ts — 地图组件专项审查 interface MapCheckResult { fpsImpact: number; // 预估帧率影响(ms) locationAccuracy: number; // 定位精度偏差(m) cacheConsistency: boolean; // 离线缓存策略是否一致 pass: boolean; } async function checkMapComponent(files: ChangedFile[]): Promise<MapCheckResult> { const mapFiles = files.filter((f) => f.path.includes("map/") || f.path.includes("location/")); if (mapFiles.length === 0) { return { fpsImpact: 0, locationAccuracy: 0, cacheConsistency: true, pass: true }; } // 帧率影响：检查是否新增了高开销渲染逻辑 let fpsImpact = 0; for (const f of mapFiles) { const heavyOps = f.content.match(/requestAnimationFrame|setInterval|setTimeout/g) ?? []; fpsImpact += heavyOps.length * 2; // 每个定时器预估2ms开销 } // 定位精度：检查是否修改了精度计算函数 const locationFiles = mapFiles.filter((f) => f.path.includes("location/")); let locationAccuracy = 0; for (const f of locationFiles) { if (f.content.match(/accuracy|precision|delta/)) { locationAccuracy += 5; // 修改精度相关代码时标记偏差 } } // 缓存一致性：检查离线策略是否被修改 const cacheFiles = mapFiles.filter((f) => f.path.includes("cache/")); const cacheConsistency = cacheFiles.every((f) => { // 确保离线缓存策略未被随意更改 const strategyPattern = /offlineStrategy|cachePolicy|tileCache/; if (strategyPattern.test(f.content)) { // 修改了缓存策略时，需要人工确认 return f.content.includes("// REVIEW-REQUIRED: cache strategy changed"); } return true; }); const pass = fpsImpact <= 8 && locationAccuracy <= 10 && cacheConsistency; return { fpsImpact, locationAccuracy, cacheConsistency, pass }; }

4.2 订单流程链路检查

订单页面涉及下单、支付、确认、取消四个阶段。变更如果跨阶段影响，属于高风险。

// order-chain-gate.ts — 订单链路完整性检查 const ORDER_STAGES = ["create", "pay", "confirm", "cancel"] as const; interface ChainImpact { affectedStages: string[]; crossStageRisk: boolean; detail: string; } function analyzeOrderChainImpact(files: ChangedFile[]): ChainImpact { const affectedStages: string[] = []; const stageDirPattern = /order\/(create|pay|confirm|cancel)/; for (const f of files) { const match = f.path.match(stageDirPattern); if (match) affectedStages.push(match[1]); } // 公共模块变更可能影响多个阶段 const sharedFiles = files.filter((f) => f.path.includes("order/shared/")); if (sharedFiles.length > 0) { affectedStages.push(...ORDER_STAGES); } const crossStageRisk = affectedStages.length >= 2; const detail = crossStageRisk ? `变更涉及 ${affectedStages.join("、")} 阶段，需验证全链路回归` : `变更仅涉及 ${affectedStages[0] ?? "无"} 阶段`; return { affectedStages, crossStageRisk, detail }; }