setup

Detect a repository's stack and validate commands to generate a .godmode/config.yaml.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill setup-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/setup
Command: npx skills add https://github.com/arbazkhan971/godmode --skill setup-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and configures project stacks and tooling so godmode can run autonomously without manual command discovery, reducing setup time and configuration errors.

Core Features & Use Cases

  • Stack Detection: Scans manifests, lockfiles, framework configs, language versions, and Docker presence to identify language, framework, and package manager.
  • Command Validation: Executes and validates test, lint, and build commands with retries, timeout handling, and fallbacks, and prints useful diagnostics on failures.
  • Platform & Optimization Setup: Identifies execution platform (Claude Code, Gemini CLI, Codex, Cursor), configures optimization metrics and scope, and writes a guarded, committed .godmode/config.yaml.
  • Use Case: Ideal for first-time repository setup or when a skill requires validated test/lint/build commands to run automated optimization or multi-agent workflows.

Quick Start

Run the setup skill to auto-detect your project's stack, validate test/lint/build commands, and commit a vetted .godmode/config.yaml.

Frequently Asked Questions about setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-detect my project stack and generate a config file?

To auto-detect your project stack and generate configuration, run the setup skill to scan manifests and lockfiles, identify your language and package manager, and commit a validated .godmode/config.yaml.

What is the best way to configure test, lint, and build commands for automated workflows?

Configuring test, lint, and build commands for automated workflows is handled by executing and validating commands with retries and fallbacks during first-time repository initialization to ensure they run successfully.

Can I use automated project detection with Docker and multiple execution platforms?

Yes, automated project detection works with Docker and multiple platforms. It identifies Docker presence for optional support and recognizes execution platforms like Claude Code, Gemini CLI, Codex, and Cursor.

Does stack detection work for repositories without standard manifests or framework configs?

Stack detection applies to projects with standard manifests, lockfiles, or framework configs. Repositories lacking these specific files may not be accurately identified, limiting the tool's ability to determine the correct toolchain.

How does command validation handle failures during project setup?

Command validation during project setup handles failures by executing test, lint, and build commands with retries, timeout handling, and fallbacks, and prints useful diagnostics if the commands ultimately fail.

Are there guardrails for storing secrets when generating a committed configuration file?

Yes, there are guardrails for storing secrets when generating a configuration file. The process enforces rules like not storing secrets and records platform and optimization settings before committing the vetted .godmode/config.yaml.