eve-repo-upkeep
97
总安装量
16
周安装量
#4409
全站排名
安装命令
npx skills add https://github.com/incept5/eve-skillpacks --skill eve-repo-upkeep
Agent 安装分布
codex
16
gemini-cli
16
claude-code
16
mcpjam
2
openhands
2
zencoder
2
Skill 文档
Eve Repo Upkeep
Use this workflow to keep an app repo current with Eve conventions.
When to Use
- After Eve platform updates or manifest schema changes
- Before a major deploy or release
- When onboarding a new maintainer
Files to Keep Current
.eve/manifest.yaml
- Ensure
schema: eve/compose/v1is present. - Prefer
services:over legacycomponents:. - Keep
x-eveingress and pipeline definitions accurate. - Keep
x-eve.defaultsin sync with harness defaults (harness/profile/options). - Keep
x-eve.agentsprofiles aligned with orchestration policy. - Ensure
x-eve.agents.config_pathandx-eve.chat.config_pathpoint to valid files. - Confirm
${secret.KEY}usage for secrets. - Deploy pipelines should include a
buildstep beforerelease. - Services with Docker images should have
build.contextdefined. - Registry auth secrets (GHCR_USERNAME, GHCR_TOKEN or GITHUB_TOKEN) should be configured.
skills.txt
- Keep Eve skillpack references up to date.
- Remove obsolete packs or pinned versions.
Agent Instructions (AGENTS.md / CLAUDE.md)
- Update skill references to include
eve-se-index. - Remove stale commands or URLs.
Agent Config Files (agents/)
agents/agents.yamldefines agents and skills.agents/teams.yamldefines team composition and dispatch.agents/chat.yamldefines chat routing rules and permissions.
Check for Deprecated Patterns
- Old CLI commands (
eve deployvseve env deploy) - Old deploy syntax without
--refparameter - Hardcoded domains in docs or manifests
- Inline secrets in repo files
- Dockerfiles missing
org.opencontainers.image.sourcelabel pointing to the repo URL - Pipelines missing
buildstep beforerelease - Services with Docker images but no
build.contextconfiguration - Missing registry authentication secrets (GHCR_USERNAME, GHCR_TOKEN/GITHUB_TOKEN)
Test After Updates
# 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.