Domain: AI / Remote Discovery
Status: Canonical
The GitHub integration enables dev.kit to perform high-fidelity Discovery by probing remote repositories, Pull Requests, and issues. By leveraging the gh CLI, it provides a grounded, authenticated interface for agents to interact with the broader engineering ecosystem.
The GitHub integration allows the Dynamic Discovery Engine to identify and resolve skills located in remote repositories.
- Trigger: Intent resolution for an authorized organization or peer repository.
- Outcome: The AI can "reach out" to remote codebases to discover patterns or standardized workflows.
- Assigned Issues: Fetches issues to ground the initial
task startphase. - PR Lifecycle: Authorizes agents to analyze and create Pull Requests to formalize drift resolution.
- CLI:
gh(GitHub CLI) must be installed and authenticated. - Auth: Prefers
GH_TOKENorGITHUB_TOKEN. Falls back to interactivegh auth login.
To maintain high-fidelity engineering flows, the GitHub integration prioritizes discovery across authoritative UDX repositories:
| Repository | Role | Purpose |
|---|---|---|
udx/reusable-workflows |
CI/CD Baseline | Canonical GitHub Action patterns and deployment templates. |
udx/wp-stateless |
Plugin Core | Reference for high-fidelity WordPress cloud integrations. |
udx/worker-deployment |
Orchestration | Standard patterns for deploying and managing the Worker Ecosystem. |
Remote discovery and collaboration are operationalized through canonical UDX resources:
| Requirement | Grounding Resource | Role |
|---|---|---|
| Patterns | udx/reusable-workflows |
Source of truth for remote discovery templates. |
| Automation | udx/worker-deployment |
Standard patterns for remote environment audits. |
Progression: [github-mesh-active]
- Step 1: Detect and verify
ghCLI health (Done) - [>] Step 2: Resolve remote repository skills (Active)
- Step 3: Perform cross-repo intent normalization (Planned)
UDX DevSecOps Team