ln-781构建验证器：自动化项目构建与编译验证工具，支持多语言

ln-781-build-verifier by levnikolaevich/claude-code-skills

209 周安装量

313 GitHub Stars

安装命令

npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-781-build-verifier

🇨🇳中文介绍

路径说明： 文件路径（shared/、references/、../ln-*）是相对于技能仓库根目录的。如果在当前工作目录未找到，请定位此 SKILL.md 文件所在目录并向上返回一级以找到仓库根目录。如果缺少 shared/ 目录，请通过 WebFetch 从 https://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path} 获取文件。

ln-781-构建验证器

类型： L3 工作器 类别： 7XX 项目引导 父级： ln-780-引导验证器

目的

检测项目类型，恢复依赖项，执行构建，并验证编译是否成功。

范围：

根据文件标记自动检测项目类型
使用适当的包管理器恢复依赖项
为每个项目执行构建命令
验证构建产物是否存在

范围之外：

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

场景	使用此技能
由 ln-780 编排器调用时	是
独立的构建验证	是
CI/CD 流水线构建步骤	是
需要执行测试时	否，请使用 ln-782

步骤 1：检测项目类型

扫描项目根目录以查找类型标记。

标记文件	项目类型	构建系统
package.json	Node.js/前端	npm/yarn/pnpm
*.csproj	.NET	dotnet
setup.py / pyproject.toml	Python	pip/poetry
go.mod	Go	go build
Cargo.toml	Rust	cargo
pom.xml	Java/Maven	mvn
build.gradle	Java/Gradle	gradle

步骤 2：恢复依赖项

为每个检测到的项目，在构建前恢复依赖项。

项目类型	依赖项恢复
Node.js	从锁文件安装包
.NET	恢复 NuGet 包
Python	从 requirements 或 pyproject 安装
Go	下载模块
Rust	获取 crate

步骤 3：构建项目

为每个项目类型以 Release/Production 模式执行构建。

项目类型	构建模式	预期结果
Node.js	Production	打包的资源位于 dist/ 或 build/ 目录
.NET	Release	编译后的 DLL 位于 bin/Release/ 目录
Python	Editable install	包已安装到环境中
Go	Production	编译后的二进制文件
Rust	Release	优化后的二进制文件位于 target/release/ 目录

步骤 4：验证构建产物

确认构建输出存在。

项目类型	产物检查
Node.js	dist/ 或 build/ 目录存在且包含文件
.NET	bin/Release/{framework}/ 目录中存在 DLL 文件
Python	包可导入
Go	二进制可执行文件存在
Rust	target/release/ 目录中存在二进制文件

步骤 5：报告结果

将结构化结果返回给编排器。

字段	描述
projectName	项目名称
projectType	检测到的类型（nodejs, dotnet, python 等）
status	success / failed
duration	构建时间（秒）
outputPath	构建产物的路径
errorMessage	失败时的错误详情

错误类型	恢复操作
依赖项恢复失败	检查网络，验证锁文件完整性
编译错误	记录完整的错误输出，报告为失败
缺少构建工具	报告需要安装的工具
超时	报告超时，建议增加限制

始终先恢复依赖项 - 没有最新的依赖项，构建可能会失败
使用生产/发布模式 - 开发构建可能隐藏问题
验证产物存在 - 成功的退出代码并不足够
报告所有项目 - 包括成功和失败的构建

所有项目类型已检测
每个项目的依赖项已恢复
每个项目的构建已执行
产物已验证存在
结果已返回给编排器

父级：../ln-780-bootstrap-verifier/SKILL.md

版本： 2.0.0 最后更新： 2026-01-10

🇺🇸English

Paths: File paths (shared/, references/, ../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root. If shared/ is missing, fetch files via WebFetch from https://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}.

ln-781-build-verifier

Type: L3 Worker Category: 7XX Project Bootstrap Parent: ln-780-bootstrap-verifier

Purpose

Detects project types, restores dependencies, executes builds, and verifies successful compilation.

Scope:

Auto-detect project types from file markers
Restore dependencies using appropriate package manager
Execute build commands for each project
Verify build artifacts exist

Out of Scope:

Running tests (handled by ln-782)
Container operations (handled by ln-783)
Workflow orchestration (handled by ln-780)

When to Use

Scenario	Use This Skill
Called by ln-780 orchestrator	Yes
Standalone build verification	Yes
CI/CD pipeline build step	Yes
Test execution needed	No, use ln-782

Workflow

Step 1: Detect Project Types

Scan project root for type markers.

Marker File	Project Type	Build System
package.json	Node.js/Frontend	npm/yarn/pnpm
*.csproj	.NET	dotnet
setup.py / pyproject.toml	Python	pip/poetry
go.mod	Go	go build
Cargo.toml	Rust	cargo
pom.xml	Java/Maven	mvn
build.gradle	Java/Gradle	gradle

Step 2: Restore Dependencies

For each detected project, restore dependencies before building.

Project Type	Dependency Restoration
Node.js	Install packages from lock file
.NET	Restore NuGet packages
Python	Install from requirements or pyproject
Go	Download modules
Rust	Fetch crates

Step 3: Build Projects

Execute build for each project type in Release/Production mode.

Project Type	Build Mode	Expected Outcome
Node.js	Production	Bundled assets in dist/ or build/
.NET	Release	Compiled DLLs in bin/Release/
Python	Editable install	Package installed in environment
Go	Production	Compiled binary
Rust	Release	Optimized binary in target/release/

Step 4: Verify Build Artifacts

Confirm build outputs exist.

Project Type	Artifact Check
Node.js	dist/ or build/ directory exists, contains files
.NET	DLL files in bin/Release/{framework}/
Python	Package importable
Go	Binary executable exists
Rust	Binary in target/release/

Step 5: Report Results

Return structured results to orchestrator.

Result Structure:

Field	Description
projectName	Name of the project
projectType	Detected type (nodejs, dotnet, python, etc.)
status	success / failed
duration	Build time in seconds
outputPath	Path to build artifacts
errorMessage	Error details if failed

Error Handling

Error Type	Recovery Action
Dependency restore failed	Check network, verify lock file integrity
Compilation errors	Log full error output, report as failed
Missing build tool	Report required tool installation
Timeout	Report timeout, suggest increasing limit

Critical Rules

Always restore dependencies first - builds may fail without fresh dependencies
Use production/release mode - development builds may hide issues
Verify artifacts exist - successful exit code is not sufficient
Report all projects - include both successful and failed builds

Definition of Done

All project types detected
Dependencies restored for each project
Build executed for each project
Artifacts verified to exist
Results returned to orchestrator

Reference Files

Parent: ../ln-780-bootstrap-verifier/SKILL.md

Version: 2.0.0 Last Updated: 2026-01-10

Weekly Installs

145

Repository

levnikolaevich/…e-skills

GitHub Stars

245

First Seen

Jan 24, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykWarn

Installed on

claude-code133

cursor130

gemini-cli129

codex129

opencode129

github-copilot124

Azure Data Explorer (Kusto) 查询技能：KQL数据分析、日志遥测与时间序列处理

130,600 周安装