Skip to content

AGENTS.md

Latest commit

 

History

History
90 lines (72 loc) · 4.22 KB

AGENTS.md

File metadata and controls

90 lines (72 loc) · 4.22 KB
Raw

AGENTS.md

Project Overview

CALL-E Integrations is a multi-ecosystem agent integration monorepo.

  • Shared local CLI capability lives in packages/cli.
  • Client-specific integrations live under packages/.
  • Ecosystem marketplace entry points live at the repository root.

Setup Commands

  • Install dependencies: pnpm install

Build and Test

  • Run all checks: pnpm check
  • Run all tests: pnpm test
  • Check the Codex plugin: pnpm --filter @call-e/codex-plugin check
  • Test the Codex plugin: pnpm --filter @call-e/codex-plugin test
  • Dry-run package output: pnpm pack:dry-run

Project-Local Skills

  • .agents/skills/github-ci-triage: project-local skill for inspecting and diagnosing GitHub Actions CI, release, deploy, and workflow failures.
  • .agents/skills/claude-plugin-reinstall: project-local skill for refreshing, reinstalling, and locally testing the CALL-E Claude Code plugin.
  • .agents/skills/change-review-agent: project-local skill for starting a read-only review agent after code modifications when explicitly requested.
  • .agents/skills/release-decision: project-local skill for deciding whether a change requires a package release, changeset, or maintainer release decision.

Productized OpenClaw skill source lives in packages/openclaw-cli-skill/skills.

Before changing standalone Skill identities, install/update origins or migration checks, follow the staged migration plan. The standalone entries are calle version 1.0.4 for the MCP/API workflow and calle-cli for CLI compatibility; CLI and plugin names remain calle. Preserve historical verification records and add new candidate evidence rather than relabeling earlier runs.

Release Decision

Before finishing any code, docs, package metadata, marketplace, plugin, or install-flow change, assess whether the change requires a package version release.

Use .agents/skills/release-decision for the release decision checklist. Report one of:

  • No release needed
  • Patch release recommended
  • Minor release recommended
  • Major release required
  • Needs maintainer decision

Include the reason, affected package(s), and whether a changeset is needed.

Repository Conventions

  • Use English for all repository-authored content, including code comments, documentation, Skill instructions, examples, test prompts, and visible metadata. Every new or rewritten passage must be in English; existing non-English text is not a precedent for adding more. Check added and rewritten text before finishing. This rule applies to repository files; communicate with the user in their preferred language.
  • Follow existing package layout and scripts before adding new tooling.
  • Follow docs/git-naming-conventions.md when naming branches, commits, monorepo package release tags, PR titles, remotes, and stash entries.
  • Before creating a new branch, validate the candidate with pnpm run check:branch-name -- --branch <type>/<short-kebab-summary> or create it through pnpm run branch:create -- <type>/<short-kebab-summary>.
  • Keep user-facing installation steps in docs/install/, with root and package README.md files linking to the relevant install guide.
  • Treat docs/install/CALL-E-installation-guide.md as the stable public install entry point for the root README.md prompt and raw GitHub URL. Do not delete, rename, or move it; if install docs are reorganized, keep this file in place and point it to the canonical guide.
  • Before changing user-facing documentation, repeated commands, install steps, package usage, or visible integration metadata, read and follow docs/documentation-maintenance.md.
  • Treat packages/cli/docs/cli-reference.md as the canonical source for calle CLI commands and parameters. When changing calle commands, flags/options, defaults, required arguments, output shape, or parameter examples, update that reference and any synchronized command guidance in the same change.
  • Before changing marketplace entry points, plugin names, visible labels, or install commands, read and follow docs/agent-integration-layout.md.