Best use case
check is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
运行提交前检查：代码格式化验证、静态检查和单元测试。在准备提交代码、检查代码质量或验证修改是否通过时使用。
Teams using check should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/check/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How check Compares
| Feature / Agent | check | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
运行提交前检查：代码格式化验证、静态检查和单元测试。在准备提交代码、检查代码质量或验证修改是否通过时使用。
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 提交前检查 开始时声明："我正在使用 check skill 运行提交前检查。" ## 执行步骤 ### 步骤 1：代码格式化检查 ```bash gofmt -s -l . ``` 如果有未格式化的文件，列出文件清单并提示运行 `gofmt -s -w .` 修复。 ### 步骤 2：静态检查 ```bash make staticcheck ``` 如果失败，列出 staticcheck 报告的问题并给出修复建议。 ### 步骤 3：单元测试 ```bash make unittest ``` 如果任何步骤失败，停止并报告错误，给出修复建议。 ## 输出格式 全部通过时： ``` ✓ gofmt — 通过 ✓ staticcheck — 通过 ✓ unittest — 通过 ``` 有失败时列出具体错误和修复建议。 ## 系统规范（AGENTS.md） 执行本 skill 时同时遵守 `AGENTS.md` 中的系统规范；与本 skill 冲突时以本 skill 为准。
Related Skills
release-check
检查发布版本号是否在三处保持一致（conf/conf.go、CHANGELOG.md、README.md）。在准备发布新版本时使用。
git-commit
遵循 Angular 规范生成 git commit 消息。在用户请求创建 commit、写 commit message 或暂存并提交时使用。典型场景：改完代码要提交前、或要求按 Angular 规范写 message 时。
gh-view
分析 GitHub issues、PRs 与 discussions，提供见解或实施指导。在用户提供 GitHub URL、issue/PR 编号或询问仓库内容时使用。典型场景：看 issue/PR 状态、拉 diff 与 checks、要结论与建议下一步时。
gen
运行代码生成并检查变更。在修改 API 规范（api-specs/ YAML）或 sandbox OpenAPI/protobuf 后使用。
ci-analyze
分析 CI 失败原因并给出修复建议。在用户提到 CI 失败、pipeline 失败、构建失败、测试失败时使用。典型场景：PR 合前 CI 红、需要根因与修复建议时。
checking-changes
Validates all code changes before committing by running format, lint, type, and unit test checks. Use after making backend (Python) or frontend (TypeScript) changes, before committing or finishing a work session.
code-review-checklist
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability
clarvia-aeo-check
Score any MCP server, API, or CLI for agent-readiness using Clarvia AEO (Agent Experience Optimization). Search 15,400+ indexed tools before adding them to your workflow.
botlearn-healthcheck
botlearn-healthcheck — BotLearn autonomous health inspector for OpenClaw instances across 5 domains (hardware, config, security, skills, autonomy); triggers on system check, health report, diagnostics, or scheduled heartbeat inspection.
time-checker
Check accurate current time, date, and timezone information for any location worldwide using time.is. Use when the user asks "what time is it in X", "current time in Y", or needs to verify timezone offsets.
citation-check-skill
A vision-enabled verification gate with web search, designed to validate claims, citations, and data in documents, images, and AI-generated content against authoritative online sources or provided documents.
checkpoint
Save and resume working state checkpoints. Captures git state, decisions made, and remaining work so you can pick up exactly where you left off — even across Conductor workspace handoffs between branches. Use when asked to "checkpoint", "save progress", "where was I", "resume", "what was I working on", or "pick up where I left off". Proactively suggest when a session is ending, the user is switching context, or before a long break. (gstack)