smithery/yatarousan0227

agent-contracts-contracts-ci

Make contract-driven agents safe to change with strict validation, architecture docs, and contract diffs in CI.

Installation

$ npx skills add smithery/yatarousan0227 --skill agent-contracts-contracts-ci

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/yatarousan0227.

npx skills add smithery/yatarousan0227

Browse all from smithery/yatarousan0227

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
short-description
Contracts in CI

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,441 B
  • docs SUMMARY.md 147 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

agent-contracts Contracts in CI

Use this skill when you want a stable workflow for changing agents safely (team + CI).

Goals

  • Catch contract mistakes early (strict=True)
  • Keep architecture up to date (visualize)
  • Review breaking contract changes (diff)

Recommended CI Checks

  1. Run tests: pytest
  2. Validate contracts (strict): agent-contracts validate --strict --module <your.nodes>
  3. Generate docs (optional): agent-contracts visualize --module <your.nodes> --output ARCHITECTURE.md
  4. Review breaking changes:

- Use agent-contracts diff between two versions/modules - If breaking changes are expected, document them in release notes

How to Use diff Practically

Pick one pattern:

  • Versioned module: keep myapp/agents/v1.py and myapp/agents/v2.py as sources for --from-module/--to-module
  • Repo tags: run agent-contracts diff in two checkouts (CI jobs) and compare outputs

Guardrails

  • Treat state as loggable; avoid secrets in slices.
  • Prefer adding new slices/fields over mutating existing meanings.

References (load only when needed)

  • docs/cli.md
  • docs/roadmap.md
  • docs/skills/official/agent-contracts-contracts-ci/references/checklist.md