maintain-cross-platform

Name: maintain-cross-platform
Availability: InStock
Author: agent-sh

Coordinate cross-platform release checks and configuration alignment across Claude Code, OpenCoder, and Codex.

951|110|Updated Jan 15, 2026

Search Tags:#automation #validation #hooks #cross-platform #releases #ci #maintain

Ready to run

npx skills add https://github.com/agent-sh/agentsys --skill maintain-cross-platform-agent-sh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: maintain-cross-platform
Source: https://github.com/agent-sh/agentsys/tree/main/meta/skills/maintain-cross-platform
Command: npx skills add https://github.com/agent-sh/agentsys --skill maintain-cross-platform-agent-sh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating releases across Claude Code, OpenCode, and Codex is error-prone; this skill provides a centralized, local framework to align configurations, validators, and tooling for cross-platform maintenance.

Core Features & Use Cases

Centralized checks and alignment across platforms
Validation and pre-push enforcement to ensure consistency
Use Case: When preparing a new AgentSys release, run validations and align version fields across all plugins and tooling.

Quick Start

Run the maintain-cross-platform checks locally to verify cross-platform release readiness.

Frequently Asked Questions about maintain-cross-platform

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate cross-platform releases across Claude Code, OpenCode, and Codex?▼

Cross-platform release validation is performed by running local checks that align version fields across plugin manifests, CI validators, and pre-push hooks for the 3-platform architecture. This ensures configuration consistency and release readiness before deployment.

What is cross-platform configuration alignment for multi-platform plugin releases?▼

Cross-platform configuration alignment synchronizes version fields and platform-specific rules across Claude Code, OpenCode, and Codex. It centralizes validation and pre-push enforcement to prevent configuration drift during AgentSys release preparation.

How do I synchronize version fields in plugin manifests and CI validators before a release?▼

To synchronize version fields, run local validation checks that verify version alignment across plugin manifests, CI validators, and pre-push hooks. The process documents platform-specific rules in SKILL.md to maintain consistency across the 3-platform architecture.

Can I use pre-push hooks to enforce cross-platform release consistency locally?▼

Yes, pre-push hooks enforce cross-platform release consistency by validating configuration alignment across Claude Code, OpenCode, and Codex before code is pushed. This local mechanism prevents version mismatches in plugin manifests and CI validators.

Why does my cross-platform release validation fail due to configuration drift across platforms?▼

Cross-platform release validation fails when version fields in plugin manifests, CI validators, or pre-push hooks are not aligned across Claude Code, OpenCode, and Codex. Running centralized local checks identifies and resolves these configuration mismatches.

What's the best way to maintain consistent tooling configurations across a 3-platform architecture?▼

The best way to maintain consistent tooling configurations is using a centralized local framework that validates and aligns configurations across Claude Code, OpenCode, and Codex. It enforces consistency through pre-push hooks and documents platform-specific rules in SKILL.md.