Code Formatting by openshift/hypershift
npx skills add https://github.com/openshift/hypershift --skill 'Code Formatting'make lint-fix 自动修复大多数代码检查问题make verify 以验证代码检查和测试均通过make verify-codespell 来捕获拼写错误不可协商的规则:每个 Go 测试名称必须严格遵循以下格式:
name: "当 <条件> 时,它应该 <预期行为>"
示例:
name: "当 NodePool 具有有效的镜像 ID 时,它应该创建 Azure 机器模板"
name: "当子网 ID 无效时,它应该返回错误"
name: "当启用加密时,它应该配置磁盘加密集"
切勿使用通用名称,例如:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
提交前:
make lint-fixmake verify(通过)make verify-codespell 检查了 Markdown每周安装次数
–
代码仓库
GitHub 星标数
515
首次出现时间
–
安全审计
make lint-fix after writing Go code to automatically fix most linting issuesmake verify to verify both linting and tests pass before committingmake verify-codespell to catch spelling errorsNON-NEGOTIABLE RULE : Every Go test name MUST follow this exact format:
name: "When <condition>, it should <expected behavior>"
Examples:
name: "When NodePool has valid image ID, it should create Azure machine template"
name: "When subnet ID is invalid, it should return error"
name: "When encryption is enabled, it should configure disk encryption set"
NEVER use generic names like:
ALWAYS use "When...it should..." format:
✅ "When NodePool has no managed identity, it should create template without identity"
✅ "When NodePool has ImageID, it should create basic Azure machine template"
✅ "When subnet ID is invalid, it should return error with subnet parse message"
Always include unit tests when creating new functions or modifying existing ones
Before committing:
make lint-fix on Go codemake verify (passes)make verify-codespellWeekly Installs
–
Repository
GitHub Stars
515
First Seen
–
Security Audits
Azure 升级评估与自动化工具 - 轻松迁移 Functions 计划、托管层级和 SKU
73,200 周安装
AI团队自动组建与任务执行工具 - Team Assemble 技能详解
438 周安装
fetch-tweet:无需JavaScript获取Twitter/X推文数据,支持原文、作者和互动统计
441 周安装
Claude Code会话分析工具 - 验证技能行为与工作流程的后验分析工具
442 周安装
Shopify自动化工作流模板 - n8n电商库存管理、订单处理和客户生命周期自动化
446 周安装
Playwright测试审查工具 - 自动化检测反模式,提升测试代码质量与覆盖率
445 周安装
App Store 预检技能:iOS/macOS 应用提交前自动检查,避免常见拒绝
440 周安装