GitHub sync and versioned rollout for shared AI agent instructions and skills
T
Théo JUSTINE
Please let teams maintain reusable AI agent instructions and skills in a selected GitHub repository, then synchronize and deploy approved versions to the agents that use them.
Use case: a general agent routes incoming requests to support, sales or billing specialists. They share business-wide writing guidelines but also have their own responsibilities and procedures. Updating one approved instruction file should update the selected agents consistently, with a visible record of which version each agent is using. Codex or Claude could help maintain these files through reviewed pull requests.
Requested workflow:
- Connect a private repository, select a branch and instruction/skill folders, including Markdown files.
- Map shared instructions and specialist instructions to selected agents/workflow AI actions and authorized sub-accounts. Show inheritance, account-specific overrides and conflicts.
- Detect approved branch changes automatically, with manual refresh available. Show the source commit, sync status, affected agents and differences from their active version.
- Preview/test a new instruction version, approve its activation, pin or restore a known-good version. Keep the last approved version if a sync fails. Handle renamed/deleted files explicitly so obsolete rules do not remain active unnoticed.
- Separate behavioral instructions from factual Knowledge Base content. Selecting a document as a knowledge source must not silently promote it to a system instruction. Incoming emails remain conversation data and cannot rewrite the agents' rules.
Example: approve a change to the support tone or onboarding procedure once; all linked support agents receive it, while the sales agent receives only its relevant guidance. Do not export mailbox contents or secrets to GitHub by default.
Related existing request for updating factual Markdown KB files via re-sync/API:
I support that request. This complementary request concerns deployment of shared behavioral instructions/skills and per-agent version visibility, beyond updating indexed knowledge documents.
HighLevel already documents reusable skills, Knowledge Bases, MCP connectors and multi-agent routing. AI Studio Git Sync handles website/app code. The proposed addition is managed GitHub synchronization and controlled activation of agent instructions, so teams do not have to copy prompts manually or wonder whether different agents are following different versions.
Log In