eve-repo-upkeep

📁 incept5/eve-skillpacks 📅 5 days ago
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/v1 is present.
  • Prefer services: over legacy components:.
  • Keep x-eve ingress and pipeline definitions accurate.
  • Keep x-eve.defaults in sync with harness defaults (harness/profile/options).
  • Keep x-eve.agents profiles aligned with orchestration policy.
  • Ensure x-eve.agents.config_path and x-eve.chat.config_path point to valid files.
  • Confirm ${secret.KEY} usage for secrets.
  • Deploy pipelines should include a build step before release.
  • Services with Docker images should have build.context defined.
  • 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.yaml defines agents and skills.
  • agents/teams.yaml defines team composition and dispatch.
  • agents/chat.yaml defines chat routing rules and permissions.

Check for Deprecated Patterns

  • Old CLI commands (eve deploy vs eve env deploy)
  • Old deploy syntax without --ref parameter
  • Hardcoded domains in docs or manifests
  • Inline secrets in repo files
  • Dockerfiles missing org.opencontainers.image.source label pointing to the repo URL
  • Pipelines missing build step before release
  • Services with Docker images but no build.context configuration
  • 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.