npx skills add https://github.com/incept5/eve-skillpacks --skill eve-repo-upkeep保持应用仓库符合 Eve 规范。各项检查相互独立——当多个区域需要关注时,可以并行运行。
快速确定哪些区域需要关注。检查以下文件是否存在以及是否看起来过时——无需深入阅读每个文件,只需记录哪些区域需要处理:
.eve/manifest.yaml — 它存在吗?模式行是 eve/compose/v1 吗?skills.txt — 它存在吗?是否有已固定或已过时的条目?AGENTS.md / CLAUDE.md — 它们引用了当前的技能吗?agents/ 目录 — agents.yaml、teams.yaml、chat.yaml 存在吗?Keep an app repo current with Eve conventions. The checks are independent — run them in parallel when multiple areas need attention.
Quickly determine which areas need attention. Check which of these files exist and whether they look stale — don't deep-read every file, just note which areas need work:
.eve/manifest.yaml — does it exist? Is the schema line eve/compose/v1?skills.txt — does it exist? Are there pinned or obsolete entries?AGENTS.md / CLAUDE.md — do they reference current skills?agents/ directory — do agents.yaml, , exist?广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
如果只有一个区域需要处理,直接处理它。否则,进入第二阶段。
为每个需要更新的区域创建一个工作进程。下面的每个工作进程描述都是独立的——一个工作进程可以独立执行其区域,无需其他工作进程的上下文。
检查并修复 .eve/manifest.yaml:
schema: eve/compose/v1。services: 而非旧的 components:。x-eve 入口和流水线定义准确。x-eve.defaults 与工具默认值(harness/profile/options)同步。x-eve.agents 配置文件与编排策略一致。x-eve.agents.config_path 和 x-eve.chat.config_path 指向有效文件。${secret.KEY} 格式。release 步骤前包含 build 步骤。build.context。REGISTRY_USERNAME + REGISTRY_PASSWORD)仅在使用自定义自带注册表时才需要。检查并修复 skills.txt:
检查并修复 AGENTS.md、CLAUDE.md 和 agents/ 配置文件:
eve-se-index。agents/agents.yaml 定义了智能体和技能——验证条目是否为最新。agents/teams.yaml 定义了团队组成和调度——验证结构。agents/chat.yaml 定义了聊天路由规则和权限——验证规则。在代码库中搜索已弃用的模式并进行修复或标记:
eve deploy 对比 eve env deploy)--ref 参数的旧部署语法org.opencontainers.image.source 标签release 步骤前缺少 build 步骤build.context 的服务REGISTRY_USERNAME、REGISTRY_PASSWORD 或提供商等效名称)所有工作进程完成后,运行最终验证:
# 本地验证(Docker Compose)
docker compose up --build
# 暂存环境部署(需要 --ref 参数,值为 40 字符的 SHA 或相对于 --repo-dir 解析的引用)
eve env deploy staging --ref main --repo-dir .
# 如果需要,使用 --direct 绕过流水线
eve env deploy staging --ref main --repo-dir . --direct
使用 eve job follow 跟踪部署任务。
每周安装次数
148
仓库
首次出现
2026年2月8日
安全审计
安装于
gemini-cli148
codex148
claude-code146
pi53
opencode31
github-copilot31
teams.yamlchat.yamlIf only one area needs work, handle it directly. Otherwise, proceed to Phase 2.
Create one worker per area that needs updating. Each worker description below is self-contained — a worker can execute its area independently without context from the others.
Check and fix .eve/manifest.yaml:
schema: eve/compose/v1 is present.services: over legacy components:.x-eve ingress and pipeline definitions accurate.x-eve.defaults in sync with harness defaults (harness/profile/options).x-eve.agents profiles aligned with orchestration policy.x-eve.agents.config_path and x-eve.chat.config_path point to valid files.${secret.KEY} usage for secrets.build step before release.build.context defined.REGISTRY_USERNAME + REGISTRY_PASSWORD) are required only for custom BYO registries.Check and fix skills.txt:
Check and fix AGENTS.md, CLAUDE.md, and agents/ config files:
eve-se-index.agents/agents.yaml defines agents and skills — verify entries are current.agents/teams.yaml defines team composition and dispatch — verify structure.agents/chat.yaml defines chat routing rules and permissions — verify rules.Search the codebase for deprecated patterns and fix or flag them:
eve deploy vs eve env deploy)--ref parameterorg.opencontainers.image.source label pointing to the repo URLbuild step before releasebuild.context configurationREGISTRY_USERNAME, REGISTRY_PASSWORD or provider-equivalent names)After all workers complete, run final verification:
# Local validation (Docker Compose)
docker compose up --build
# Staging deploy (requires --ref with 40-char SHA or a ref resolved against --repo-dir)
eve env deploy staging --ref main --repo-dir .
# Use --direct to bypass pipeline if needed
eve env deploy staging --ref main --repo-dir . --direct
Track the deploy job with eve job follow.
Weekly Installs
148
Repository
First Seen
Feb 8, 2026
Security Audits
Installed on
gemini-cli148
codex148
claude-code146
pi53
opencode31
github-copilot31
Azure Data Explorer (Kusto) 查询技能:KQL数据分析、日志遥测与时间序列处理
128,400 周安装