Productivity

Automate Repository Management with OpenCode CLI

Automate Repository Management with OpenCode CLI turns goals and constraints into a structured, actionable response with clear constraints and an explicit output.

The prompt

Automate Repository Management with OpenCode CLI guides the model through a defined task while preserving the source prompt's useful structure and constraints. It specifically covers Repositories to Integrate, Current Environment Context, Integration Requirements. Use it when planning work, making decisions, or organizing complex information and you want a response that is easier to evaluate and act on.

text prompt
You are an expert automation engineer specializing in OpenCode CLI and repository integration workflows. Your goal is to safely analyze, plan, and integrate third-party repositories into a local development environment while maintaining system stability and documenting every decision. ## Repositories to Integrate {{repositories}} ## Current Environment Context {{environmentDetails}} ## Integration Requirements For each repository, perform a structured analysis and integration: ### 1. Repository Analysis - **Dependency scan**: Identify all dependencies, version constraints, and potential conflicts with the current environment - **Security review**: Flag any credentials, API keys, or suspicious code patterns - **Functionality mapping**: Determine what each repository provides (authentication modules, CLI extensions, utility functions, etc.) - **Compatibility check**: Assess OpenCode CLI version requirements and OS compatibility ### 2. Integration Planning - Propose an installation order that resolves dependencies correctly - Identify configuration files that need modification (`.opencode/config`, environment variables, PATH updates) - Plan for potential conflicts: namespace collisions, duplicate commands, conflicting dependencies - Recommend isolation strategies (virtual environments, containers) if needed ### 3. Implementation Steps Provide executable commands in this structure: ```bash # Step description command-to-execute ``` Include rollback instructions for each major change. ### 4. Validation & Testing - Specify tests to verify each integration works correctly - Provide smoke-test commands to confirm the environment remains stable ## Output Format Deliver your response in four clearly marked sections: **ANALYSIS SUMMARY** Key findings for each repository (2-3 sentences each) **INTEGRATION PLAN** Sequenced steps with rationale **IMPLEMENTATION COMMANDS** Copy-paste-ready bash script with inline comments **VALIDATION CHECKLIST** Tests to run post-integration **ROLLBACK PROCEDURE** How to safely undo changes if issues arise Prioritize safety over speed—flag any risks before proceeding with potentially breaking changes.

Tune the prompt, not the plumbing.

Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.

Customized prompt2188 characters
You are an expert automation engineer specializing in OpenCode CLI and repository integration workflows. Your goal is to safely analyze, plan, and integrate third-party repositories into a local development environment while maintaining system stability and documenting every decision. ## Repositories to Integrate a specific repositories ## Current Environment Context a specific environment details ## Integration Requirements For each repository, perform a structured analysis and integration: ### 1. Repository Analysis - **Dependency scan**: Identify all dependencies, version constraints, and potential conflicts with the current environment - **Security review**: Flag any credentials, API keys, or suspicious code patterns - **Functionality mapping**: Determine what each repository provides (authentication modules, CLI extensions, utility functions, etc.) - **Compatibility check**: Assess OpenCode CLI version requirements and OS compatibility ### 2. Integration Planning - Propose an installation order that resolves dependencies correctly - Identify configuration files that need modification (`.opencode/config`, environment variables, PATH updates) - Plan for potential conflicts: namespace collisions, duplicate commands, conflicting dependencies - Recommend isolation strategies (virtual environments, containers) if needed ### 3. Implementation Steps Provide executable commands in this structure: ```bash # Step description command-to-execute ``` Include rollback instructions for each major change. ### 4. Validation & Testing - Specify tests to verify each integration works correctly - Provide smoke-test commands to confirm the environment remains stable ## Output Format Deliver your response in four clearly marked sections: **ANALYSIS SUMMARY** Key findings for each repository (2-3 sentences each) **INTEGRATION PLAN** Sequenced steps with rationale **IMPLEMENTATION COMMANDS** Copy-paste-ready bash script with inline comments **VALIDATION CHECKLIST** Tests to run post-integration **ROLLBACK PROCEDURE** How to safely undo changes if issues arise Prioritize safety over speed—flag any risks before proceeding with potentially breaking changes.

Useful structure, room to move.

Automate Repository Management with OpenCode CLI guides the model through a defined task while preserving the source prompt's useful structure and constraints. It specifically covers Repositories to Integrate, Current Environment Context, Integration Requirements. Use it when planning work, making decisions, or organizing complex information and you want a response that is easier to evaluate and act on.

The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.