east-contribute

Manage end-to-end contribution workflows for the East monorepo across TypeScript, Python, and C.

Updated Nov 10, 2025
One-click install
npx skills add https://github.com/elaraai/east-workspace --skill east-contribute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: east-contribute
Source: https://github.com/elaraai/east-workspace/tree/main/libs/east-claude-plugin/skills/east-contribute
Command: npx skills add https://github.com/elaraai/east-workspace --skill east-contribute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the complex process of contributing to the East monorepo, preventing common pitfalls like capability duplication, broken East idioms, and missed CI gates.

Core Features & Use Cases

  • Issue-to-PR Workflow: Guides you through the entire lifecycle of a contribution, from triaging a GitHub issue to verifying the final pull request.
  • Anti-Duplication Discovery: Provides a rigorous search procedure to ensure new capabilities aren't already implemented elsewhere in the platform.
  • Compliance Enforcement: Automates the verification of East-specific standards, including TypeDoc requirements, interop rules, and CI-enforced diagnostics.

Quick Start

Use the east-contribute skill to work on issue number 42 in the elaraai/east-workspace repository.

Frequently Asked Questions about east-contribute

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

FAQPage Schema
How do I contribute changes to a TypeScript monorepo without breaking CI?

Contributing changes to a TypeScript monorepo without breaking CI requires following an end-to-end workflow that enforces type safety, idiomatic consistency, and automated diagnostic gates. This verifies all code changes meet strict platform standards before merging.

What is the best way to prevent capability duplication when adding features to a monorepo?

The best way to prevent capability duplication in a monorepo is running a rigorous discovery search procedure before implementation. This verifies new capabilities are not already implemented elsewhere in the platform, avoiding redundant code contributions.

How do I manage an issue-to-PR workflow across TypeScript, Python, and C runtimes?

Managing an issue-to-PR workflow across TypeScript, Python, and C runtimes requires guiding the contribution lifecycle from issue triage through implementation to final pull request verification. This enforces interop rules and TypeDoc requirements across all runtimes.

Does this contribution workflow enforce TypeDoc requirements and interop rules?

Yes, the contribution workflow enforces East-specific standards including TypeDoc requirements and interop rules. It automates verification of CI-enforced diagnostics to ensure all contributions maintain full test coverage and type safety.

Why does my monorepo contribution fail CI diagnostics during verification?

Your monorepo contribution fails CI diagnostics during verification when it does not adhere to strict platform standards. The workflow enforces automated diagnostic gates to ensure type safety, idiomatic consistency, and full test coverage are met.