- Kickstart tutorial
- Must-read tutorial: the concepts of branching and merging note the collaborating link at the bottom
- A branching top-down view
- How to resolve merge conflicts in Git? - Stack Overflow Very good hints below the solution.
- Github's help for merging from commandline
| // Updated: Aug. 20, 2024 | |
| // Run: node testRegex.js whatever.txt | |
| // Live demo: https://jina.ai/tokenizer | |
| // LICENSE: Apache-2.0 (https://www.apache.org/licenses/LICENSE-2.0) | |
| // COPYRIGHT: Jina AI | |
| const fs = require('fs'); | |
| const util = require('util'); | |
| // Define variables for magic numbers | |
| const MAX_HEADING_LENGTH = 7; |
How systematic methodology and architectural understanding enabled the successful migration of 12 specialized AI agents between platforms, creating reusable patterns for future migrations
Migrating AI agents between platforms isn't just a technical exercise—it's an architectural transformation. When you port agents from one system to another, you're not simply copying code; you're translating between different philosophies of agent interaction, tool management, and capability expression.
A fire-and-forget workflow that takes a Linear issue ID and autonomously plans, tests, implements, and opens a draft PR — with TDD baked in. You walk away; it notifies you when done.
Built for OpenCode using custom agents and slash commands.
Important: The
/workflowcommand must run withagent: build(OpenCode's default agent with full tool access). The orchestrator needs unrestricted access to do git operations, dispatch subagents, and create PRs. If you're in a restricted mode, switch to build first.
Why this exists:
- Fire and forget. Kick off a task and walk away. You get notified when it's done or needs attention.