Monoco Core
Core features and commands of Monoco Toolkit.
Overview
Monoco is a developer productivity toolkit providing:
- •Project Initialization: Standardized project structure
- •Configuration Management: Global and project-level configuration
- •Workspace Management: Multi-project setup
Core Commands
Project Setup
- •
monoco init: Initialize a new Monoco project- •Creates
.monoco/directory with default configuration - •Sets up project structure (Issues/, .references/, etc.)
- •Generates initial documentation
- •Creates
Configuration Management
- •
monoco config: Manage configuration- •
monoco config get <key>: View configuration value - •
monoco config set <key> <value>: Update configuration - •Supports global (
~/.monoco/config.yaml) and project (.monoco/config.yaml) scopes
- •
Agent Integration
- •
monoco sync: Sync with agent environment- •Injects system prompts into agent configuration files (GEMINI.md, CLAUDE.md, etc.)
- •Distributes skills to agent framework directories
- •Follows
i18n.source_langlanguage configuration
- •
monoco uninstall: Clean up agent integration- •Removes managed blocks from agent configuration files
- •Cleans up distributed skills
Git Workflow Integration
Monoco enforces Feature Branch Workflow to ensure code isolation and quality:
- •
monoco init: Automatically installs Git Hooks- •pre-commit: Runs Issue Linter and code format checks
- •pre-push: Executes test suite and integrity validation
- •All Hooks can be configured via
.monoco/config.yaml
- •
Branch Isolation Strategy:
- •⚠️ Mandatory: Use
monoco issue start <ID> --branchto create isolated environment - •Automatically creates standardized branch name:
feat/<id>-<slug> - •Main Branch Protection: Linter prevents direct code modifications on
main/masterbranches
- •⚠️ Mandatory: Use
- •
File Tracking:
monoco issue sync-filesautomatically syncs Git changes to Issue metadata
📖 Detailed Workflow: See
monoco-issueskill for complete Issue lifecycle management guide.
Configuration Structure
Configuration is stored in YAML format at:
- •Global:
~/.monoco/config.yaml - •Project:
.monoco/config.yaml
Key configuration sections:
- •
core: Editor, log level, author - •
paths: Directory paths (issues, spikes, specs) - •
project: Project metadata, spike repos, workspace members - •
i18n: Internationalization settings - •
agent: Agent framework integration settings
Best Practices
Basic Operations
- •Prioritize CLI commands over manual file editing
- •Run
monoco syncafter configuration changes to update agent environment - •Commit
.monoco/config.yamlto version control to maintain team consistency - •Keep global configuration minimal - most settings should be project-specific
Git Workflow (⚠️ CRITICAL for Agents)
- •
Strictly follow branch isolation:
- •✅ Always use:
monoco issue start <ID> --branch - •❌ Prohibited from directly modifying code on
main/masterbranches - •📝 Before committing run:
monoco issue sync-filesto update file tracking
- •✅ Always use:
- •
Quality Gates:
- •Git Hooks automatically run checks, do not attempt to bypass (
--no-verify) - •Ensure
monoco issue lintpasses before committing - •Use
monoco issue submitto generate delivery report
- •Git Hooks automatically run checks, do not attempt to bypass (