Welcome! You're about to learn something powerful and exciting. COSMOS is your complete automation suite for multi-language monoreposβhandling everything from code validation to cloud deployments, issue tracking, and intelligent release orchestration.
You'll complete your first complete workflow:
Time needed: 45-60 minutes for complete setup
What you'll learn: The full professional development workflow
Before anything else, you need a GitHub account. GitHub is where all our code lives online.
Skip to Step 1! π
https://github.com/signupβ You now have a GitHub account!
Don't skip this! Once your account is created, you need permission:
The terminal is how you talk to your computer using text commands instead of clicking.
Command + Space (opens Spotlight)terminalUse Git Bash (not Command Prompt or PowerShell):
https://git-scm.com/downloadsA window with text ending in a $ or > symbol. This is your promptβwhere you type commands.
COSMOS works in any editor. But for your first mission, we recommend Visual Studio Code because:
Using Sublime, Vim, or another editor? That works too. COSMOS validates outside the editor, so your choice doesn't matter. But we recommend Code for the best first experience.
You need to authenticate with GitHub before you can download code.
Press
1. "What account do you want to log into?"
β Type 1 and press Enter (GitHub.com)
2. "What is your preferred protocol?"
β Type 1 and press Enter (HTTPS)
3. "Authenticate Git with your GitHub credentials?"
β Type y and press Enter
4. "How would you like to authenticate?"
β Type 1 and press Enter
ABCD-1234)β Success! Terminal shows: "β Logged in as [your username]"
Now we're getting the actual code to your computer.
Press
β Replace with your actual repository URL!
Press
Press
Press
You should see: install.sh, various .sh files, and directories.
β Perfect! You're in the repository.
The installer now includes membrane generation, cloud setup, and issue tracking.
Press
The installer will guide you through:
The installer will ask: "Generate .cosmos-membrane.json?"
The membrane is a global ecosystem configuration that:
y to generate:.cosmos-membrane.json~/.cosmos/membrane.jsonβ Membrane created! This powers all intelligent features.
fzf installed, COSMOS will use it for fuzzy repository search with interactive selection!
The installer will ask: "Configure cloud infrastructure?"
COSMOS integrates with your cloud provider to:
us-central1-docker.pkg.dev
*.dkr.ecr.*.amazonaws.com
*.azurecr.io
docker.io
y to configure:1 (GCP)veps-service-480701β
Configuration saved to .cosmos.cloud.env
c-cloud-setup
The installer will ask: "Configure issue tracking?"
COSMOS includes a powerful issue management system with:
y to configure:1 (GitHub)β
Saved to .cosmos.issue.env
β
Issue templates created in .cosmos/issue-templates/
Press
You should see: A formatted table showing the status of all services with language badges, versions, and sync status.
Membrane-aware status monitor showing all services with intelligent discovery
c-pulse
Save changes with automatic validation and conventional formatting
c-commit
Preview a release before creating itβshows version and changelog
c-test <service>
Cloud-aware release orchestration with GitHub Actions coordination
c-linker <service>
Deep analysis of services with manifest awareness
c-audit <service>
Create and manage issues with intelligent repository discovery
c-issue
Configure or reconfigure cloud infrastructure
c-cloud-setup
Create cosmos.json manifest for documentation projects
cosmos-init.sh
COSMOS automatically detects and validates multiple programming languages plus documentation:
Cargo.tomlcargo check[RUST]
package.jsonnpm run lint[NODE]
go.modgo build ./...[GO]
pom.xmlmvn compile
build.gradlegradle build
pyproject.tomlpython -m py_compile
cosmos.json for documentation-only projects!
Let's practice the daily workflow. You'll edit a file and use COSMOS to save it properly.
Press
For this example, create a simple text file:
Press
Press
β You've modified a real file!
This is where COSMOS makes your life easier. It validates, formats, and saves your changes properly.
Press
The --no-verify flag: Skips validation since we're changing documentation, not code.
1. "Selection:"
β Type 4 and press Enter (documentation change)
2. "Message:"
β Type: add myself to newcomers registry
β Press Enter
3. "Scope:"
β Just press Enter (auto-fills)
4. "Finalize?"
β You'll see your formatted message
β Type y and press Enter
β Success! You'll see: "β Commit successful!"
docs(scope): your messageUpload your change to GitHub so everyone can see it.
Press
Press
β Your change is now on GitHub!
You just completed your first real workflow:
That's genuinely impressive!
Now you know the four-step workflow you'll use every day:
Edit files however you normally would
This time without --no-verify. COSMOS will validate your code before saving. For code changes, it will run language-specific checks (cargo check, npm lint, etc.).
That's it! Four simple steps instead of remembering all the git commands.
Once you're comfortable with the basics, you can explore:
Shows all services, their versions, and release status
See what version and changelog would be created (no changes made)
Release a service version with automatic constraint checking and GitHub Actions coordination. Then push with git push --follow-tags
See detailed history and version information
Q: What if I make a mistake?
A: Don't panic! Everything is tracked and reversible. You can't break anything permanently.
Q: What if I see an error?
A: Read it carefullyβmost errors tell you exactly what's wrong. Common fixes:
cd ~/Code/roxy-systems./install.shQ: Can I practice the commit workflow again?
A: Absolutely! Make more changes and repeat the c-commit β git push flow.
Q: What does c-linker do?
A: It coordinates releases with GitHub Actions. It checks that security scans pass, validates dependencies, and creates release tags. Your workflow triggers the AP (Application Plane) workflow to build Docker images and sign them.
Q: What is cosmos.json?
A: An optional manifest file for documenting projects and custom types. Create it later with cosmos-init.sh when you're ready.
Q: Who do I ask for help?
A: Your team lead or team chat. Everyone was new onceβasking questions is normal!
Take your time: No rush. Go at your own pace.
You can't break anything: Seriously. Worst case is an error message and you try again.
Every expert started here: Every great developer was once typing their first terminal command.
You're doing great: If you made it this far, you're already learning!
c-commit β git push workflow several timesc-pulse to see the full project statusc-test for previewing releasesc-linkercosmos.json manifest with cosmos-init.shYou've got this! π
COSMOS Multi-Language Quick Start Guide v2.3
Updated with Manifest-Aware Edition & Defensive Installation