Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
God's eye view of your dev repos. Multi-project tracking across GitHub/Azure DevOps. AI learns from your commits to upgrade your agents.md.
God's eye view of your dev repos. Multi-project tracking across GitHub/Azure DevOps. AI learns from your commits to upgrade your agents.md.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Conversational project oversight and AI agent coaching for OpenClaw.
god-mode lets users ask about their projects in plain English. You run the commands and explain the results conversationally. What users can ask: "Set up god-mode for my repos" "What's happening across my projects?" "Which repos need attention?" "Analyze my agents.md" "What should I work on today?" What you provide: Multi-project status summaries (GitHub + Azure DevOps) Plain-English explanations of commit activity, PRs, issues LLM-powered agent instruction analysis Recommendations for improving their AGENTS.md Perfect for: Developers juggling multiple repos who want conversational oversight Teams using AI coding assistants (Claude, Copilot, etc.) Anyone who wants data-driven improvements to their AGENTS.md
Just tell me what you want! I'll run the god-mode commands for you. Example conversations: You: "Set up god-mode for my tada repository" Me: Sure! I'll set up god-mode and add your tada repo. [runs god setup and god projects add github:YourUsername/tada] Done! Your repo is configured. Want me to sync the data? You: "Yes, and show me what's happening" Me: [runs god sync and god status] Here's your overview: tada: 30 commits this week, last activity 3 days ago 0 open PRs, 0 issues Your most active project! Commits are all features and bug fixes. You: "Analyze my agents.md for tada" Me: [runs god agents analyze github:YourUsername/tada] I've analyzed your AGENTS.md against 155 commits. Here's what I found: GAPS: Testing practices (high impact) - 68 bug fixes but no testing guidance Voice API debugging - 12 commits mention "voice" but no troubleshooting STRENGTHS: TypeScript strictness is working - zero type-related fixes Want me to add testing guidance to your AGENTS.md? What you can ask me: "Set up god-mode for [repo]" "Show me all my projects" "What's happening across my repos?" "Analyze my agents.md" "Which repos need attention?" "What should I work on today?" I'll handle all the commands and explain the results in plain English.
If you prefer running commands yourself: # Setup god setup # Add a project god projects add github:username/repo # Sync and view god sync god status
Show overview of all projects, or details for one: god status # All projects god status myproject # One project in detail
Fetch/update data from repositories: god sync # Incremental sync all god sync myproject # Just one project god sync --force # Full refresh (ignore cache)
Manage configured projects: god projects # List all god projects add github:user/repo # Add project god projects remove myproject # Remove project
Generate monthly activity reviews: god review # Last month's activity god review --month 2026-01 # Specific month god review --json # JSON output What it shows: Total commits across all projects Most active repositories Pull request activity (merged, active, closed) Detailed breakdown by project with date ranges Perfect for monthly retrospectives and planning Example output: Monthly Review: 2026-01 ๐ 286 commits across 7 projects ๐ฅ 10 unique contributors Most Active Projects: tada - 155 commits ContentEngine - 63 commits brain - 27 commits Use cases: Monthly team stand-ups Personal retrospectives ("What did I actually work on?") Quarterly planning ("Which projects got attention?") Automated monthly summaries via cron
Analyze agents.md against commit history using LLM: god agents analyze myproject What it does: Fetches your AGENTS.md from the repository Analyzes commit patterns (types, pain points, frequently changed files) Calls an LLM (Claude/GPT) to find gaps and suggest improvements Displays recommendations interactively Optionally applies changes to your AGENTS.md LLM Configuration: god-mode automatically detects and uses the best available LLM: OpenClaw (default when running as skill) - Uses your OpenClaw agent Anthropic - Set ANTHROPIC_API_KEY="sk-ant-..." OpenAI - Set OPENAI_API_KEY="sk-..." OpenRouter - Set OPENROUTER_API_KEY="sk-or-..." Manual - Outputs prompt if no LLM available When running in OpenClaw: The analysis prompt is displayed to your OpenClaw agent You (or your agent) provides the JSON analysis directly in the conversation Much simpler than managing separate API keys! OpenClaw Workflow: When you run god agents analyze in OpenClaw: Analysis starts: ๐ญ Analyzing github:InfantLab/tada โ Found AGENTS.md (remote) โ 155 commits analyzed ๐ค Using OpenClaw's LLM I (OpenClaw agent) receive the analysis prompt showing: Your complete AGENTS.md content Commit pattern summary (45 features, 68 bug fixes, etc.) Most changed files/directories Pain points and commit samples I analyze and provide JSON response: { "gaps": [ { "area": "Testing", "observation": "68 bug fixes but no testing guidance in AGENTS.md", "impact": "high", "suggestion": "Add testing section with coverage targets" } ], "strengths": [...], "recommendations": [...] } god-mode displays results and offers to apply changes to your AGENTS.md You choose which recommendations to accept, and god-mode updates the file Standalone Workflow (outside OpenClaw): If you set ANTHROPIC_API_KEY or OPENAI_API_KEY, god-mode calls the API directly: export ANTHROPIC_API_KEY="sk-ant-..." god agents analyze myproject # Fully automated
Bootstrap agents.md for a new project by analyzing repo structure.
View activity logs: god logs # Last 50 lines god logs -n 100 # Last 100 lines god logs -f # Follow log output god logs --path # Show log file location god logs --clear # Clear all logs All god-mode activity is logged to ~/.god-mode/logs/activity.log with timestamps for transparency and debugging.
Config file: ~/.config/god-mode/config.yaml projects: - id: github:user/repo name: My Project # Display name priority: high # high/medium/low tags: [work, api] local: ~/code/myrepo # Local clone path sync: initialDays: 90 # First sync lookback commitsCacheMinutes: 60 analysis: agentFiles: # Files to search for - agents.md - AGENTS.md - CLAUDE.md - .github/copilot-instructions.md
All data stored locally in ~/.god-mode/: cache.db - SQLite database (commits, PRs, issues, analyses) contexts/ - Saved workspace contexts (v0.2)
god-mode uses your existing CLI authentication: ProviderCLISetupGitHubghgh auth loginAzureazaz loginGitLabglabglab auth login No tokens stored by god-mode. We delegate to CLIs you already trust.
gh - GitHub CLI (for GitHub repos) sqlite3 - Database jq - JSON processing
god status # See all projects at a glance # Notice any stale PRs or quiet projects
god status myproject # See recent activity, open PRs, issues # Remember where you left off
god agents analyze myproject # Get suggestions based on your actual commit patterns # Apply recommendations to your agents.md
god status # Review activity across all projects # Identify projects needing attention
When the user asks about their projects, here's what to do:
Run god setup (checks dependencies) Run god projects add github:username/repo Run god sync to fetch data Summarize what you found
Run god status Translate output to conversational summary: "Your most active repo is X with Y commits this week" "Z repo hasn't had activity in N days" "You have M open PRs across all projects"
Run god agents analyze github:username/repo You'll receive the analysis prompt with: Their complete AGENTS.md Commit pattern analysis (155 commits, 68 bug fixes, etc.) Pain points and frequently changed files Provide JSON analysis in this format: { "gaps": [ {"area": "Testing", "observation": "68 bug fixes but no test guidance", "impact": "high", "suggestion": "Add testing section"} ], "strengths": [ {"area": "TypeScript", "observation": "Zero type errors in 155 commits"} ], "recommendations": [ {"priority": 1, "section": "## Testing", "content": "- Write unit tests for new code\n- Run tests before commits"} ], "summary": "Strong TypeScript practices, needs testing guidance" } Summarize the analysis conversationally Offer to apply recommendations
Run god status Look for: Stale PRs (>3 days old) No activity in >5 days Open issues piling up Suggest what to focus on
In OpenClaw: Just ask me! "Show me my projects", "Analyze my agents.md", etc. I'll run the commands and explain the results. CLI: Run commands directly: god status, god sync, god agents analyze
First time: Tell me to "set up god-mode for [your repo]" and I'll handle it. Or run god setup and god projects add github:your/repo yourself. Authentication: Make sure gh auth login is done (GitHub CLI authentication).
No! When you ask me to analyze your agents.md, I receive the analysis prompt and provide the JSON response directly. No separate API key needed. Standalone: If using god-mode outside OpenClaw, you can set ANTHROPIC_API_KEY or OPENAI_API_KEY for automated analysis.
When you ask: I run god sync when you ask about your projects. First sync fetches 90 days of history. Subsequent syncs are incremental (only new data). Manual: You can run god sync anytime, or god sync --force for a full refresh.
Locally only: Commits, PRs, issues, and analysis results in ~/.god-mode/cache.db. Activity logs in ~/.god-mode/logs/activity.log. Nothing sent to external servers (except when calling LLM APIs if configured).
Yes! Uses your gh CLI authentication, so it has access to whatever your GitHub account can access.
Install GitHub CLI: https://cli.github.com/
Run: gh auth login
Add a project: god projects add github:user/repo
Force refresh: god sync --force
This is normal in OpenClaw mode - the prompt is displayed for the OpenClaw agent to analyze. The agent provides the JSON response in conversation, not as return value. OpenClaw Community Skill License: MIT Repository: https://github.com/InfantLab/god-mode-skill
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.