godmode

In the author's own words, from each skill's SKILL.md — showing the first 30 of 33 files.

• agent-briefing

  Use when writing a prompt for a subagent or teammate, deciding how much context another agent needs, writing or reading a handoff report between agents, or sending a message to another agent mid-task.

  skills/agent-briefing/SKILL.md on GitHub (opens in a new tab)

• code-review

  Use when a task, feature or bug fix is implemented and before it is committed, merged or handed back to the user, and when the user asks for a review of a change, a branch or a pull request.

  skills/code-review/SKILL.md on GitHub (opens in a new tab)

• codebase-conventions

  Use when about to add or change code in an existing codebase: a new file, module, route, component, service, test, migration, error path or dependency, especially in a project the agent did not write or has not yet surveyed in this session.

  skills/codebase-conventions/SKILL.md on GitHub (opens in a new tab)

• completion-gate

  Use when about to say that work is done, fixed, passing, working, deployed or ready, before committing, opening or merging a pull request, closing a task, moving to the next task, or reporting a subagent's result as finished.

  skills/completion-gate/SKILL.md on GitHub (opens in a new tab)

• cross-model-review

  Use when a reviewed change is about to land on a shared branch, be released or be deployed, and when the user asks for a second opinion on a change from a different model or a different AI vendor.

  skills/cross-model-review/SKILL.md on GitHub (opens in a new tab)

• delegated-execution

  Use when a written implementation plan is ready to execute in the current session and its tasks are mostly independent, so each one can go to a fresh implementer subagent with its own review.

  skills/delegated-execution/SKILL.md on GitHub (opens in a new tab)

• doctor

  Use when GodMode skills do not seem to trigger, when the user asks whether GodMode is installed or working, or after installing or updating the plugin on any harness

  skills/doctor/SKILL.md on GitHub (opens in a new tab)

• environment-awareness

  Use when about to run the first shell command in a session or a new project, when installing dependencies, when a command fails with not found or not recognised, when writing platform-specific code or paths, or when entering a container, virtual machine, remote host or CI runner.

  skills/environment-awareness/SKILL.md on GitHub (opens in a new tab)

• error-recovery

  Use when a fix attempt has failed more than once for the same problem, when a fix for one problem causes another, when the same file keeps being edited without progress, when test results get worse, or when the work feels stuck in a loop.

  skills/error-recovery/SKILL.md on GitHub (opens in a new tab)

• fault-diagnosis

  Use when a test fails, a build breaks, a bug is reported, behaviour is unexpected, performance degrades or an integration stops working, before proposing or making any fix.

  skills/fault-diagnosis/SKILL.md on GitHub (opens in a new tab)

• grounding

  Use when about to write code, config or commands against a library, API, CLI, SDK, model or platform, or to state a version, flag, limit, price, licence, release date or best practice to the user, or when an error suggests an interface has changed

  skills/grounding/SKILL.md on GitHub (opens in a new tab)

• inline-execution

  Use when a written implementation plan is to be executed by the current agent itself rather than by subagents: the user chose the cheaper mode, the harness cannot dispatch subagents, or the plan is short and fully specified.

  skills/inline-execution/SKILL.md on GitHub (opens in a new tab)

• intent-discovery

  Use when the user wants something new built or existing behaviour changed, such as a feature, component, page, API, module or project, and no approved design for it exists yet in this conversation or in docs/plans

  skills/intent-discovery/SKILL.md on GitHub (opens in a new tab)

• knowledge-capture

  Use when a substantial task finishes, when the user corrects the agent or states a preference, when a non-obvious cause or project convention is discovered the hard way, or when the user asks the agent to remember or forget something

  skills/knowledge-capture/SKILL.md on GitHub (opens in a new tab)

• merge-protocol

  Use when implementation on a branch is finished and reviewed and the work needs to land, be proposed as a pull request, be parked for later, or be thrown away.

  skills/merge-protocol/SKILL.md on GitHub (opens in a new tab)

• model-routing

  Use when dispatching any subagent, teammate or reviewer, choosing a model or effort level for a piece of delegated work, escalating after an agent fails, or when a run's token or quota budget matters.

  skills/model-routing/SKILL.md on GitHub (opens in a new tab)

• parallel-execution

  Use when two or more problems can each be solved without the others' results or shared state, such as unrelated test failures in separate subsystems, independent investigations, or separate modules with no common files.

  skills/parallel-execution/SKILL.md on GitHub (opens in a new tab)

• performance-tuning

  Use when something is reported slow, sluggish, memory-hungry or too large, when a performance budget, Core Web Vitals threshold or latency target is breached, when asked to optimise or make code faster, or when tempted to add a cache, index, async rewrite or micro-optimisation.

  skills/performance-tuning/SKILL.md on GitHub (opens in a new tab)

• project-bootstrap

  Use when creating a new project or repository, scaffolding a codebase from nothing, turning a prototype into something that will be kept, or inheriting a project that has no version control hygiene, formatter, linter, tests or CI.

  skills/project-bootstrap/SKILL.md on GitHub (opens in a new tab)

• quality-gates

  Use when setting up or changing a project's lint, type, test, coverage, build, size, audit, complexity or dead-code checks, when a commit, pull request or merge is being prepared, and when a check fails or someone proposes to disable, skip or loosen one.

  skills/quality-gates/SKILL.md on GitHub (opens in a new tab)

• rationale

  Use when the user asks for new work such as a feature, component, integration, service or dependency, especially when the request names a solution instead of a problem, the scope looks larger than the user may expect, or the motivation is that other products have it

  skills/rationale/SKILL.md on GitHub (opens in a new tab)

• reference-first

  Use when about to design or build an API, database schema, test strategy, CI pipeline, architecture, library integration or any feature that plausibly exists already as open source, a public standard or a well-known product's published design, and no proven reference has been named yet.

  skills/reference-first/SKILL.md on GitHub (opens in a new tab)

• review-response

  Use when code review feedback arrives from the user, a reviewer subagent, another model, a human colleague or an automated tool, before changing any code in response, and especially when the feedback is unclear, looks wrong, or contains several items that may depend on each other.

  skills/review-response/SKILL.md on GitHub (opens in a new tab)

• security-protocol

  Use when writing or changing code that handles user input, uploaded files, authentication, sessions, authorisation, database queries, shell commands, file paths, outbound requests to user-supplied URLs, HTTP responses and headers, secrets or credentials, deserialisation, or new third-party dependencies.

  skills/security-protocol/SKILL.md on GitHub (opens in a new tab)

• system-design

  Use when choosing or changing architecture, a database, an API style, authentication, caching, queues or background jobs, file and module organisation, hosting, or any external service, or when the user asks what to use, where to deploy, how to scale, or whether to split into services.

  skills/system-design/SKILL.md on GitHub (opens in a new tab)

• task-planning

  Use when an approved design, specification or clear requirement exists for work that touches more than one file or behaviour, before any implementation code is written

  skills/task-planning/SKILL.md on GitHub (opens in a new tab)

• team-orchestration

  Use when a task needs several agents that must coordinate with each other while they work, such as negotiating an interface across layers, debating competing hypotheses, or redirecting each other's research, and the harness supports agent teams.

  skills/team-orchestration/SKILL.md on GitHub (opens in a new tab)

• test-first

  Use when implementing a feature, fixing a bug, refactoring, or changing behaviour in any codebase, before writing the production code that does it.

  skills/test-first/SKILL.md on GitHub (opens in a new tab)

• ui-engineering

  Use when writing or changing frontend component code, page layouts, forms, client state, responsive behaviour, animation or styling, or when working in a codebase that uses a design system or component library such as shadcn/ui, Material UI, Ant Design, Chakra UI or Mantine.

  skills/ui-engineering/SKILL.md on GitHub (opens in a new tab)

• ui-research

  Use when about to design or build any user interface: a website, landing page, web or mobile app screen, dashboard, admin panel, form, game menu or HUD, or a single new component, and no layout reference, design tokens or established design system has been identified for it yet.

  skills/ui-research/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• elephant-goldfish-modelby google Open-source skills for designing and reviewing software with AI agents 12.4k stars · 7 skills
• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 185k stars · 6 skills
• awesome-claude-skillsby ComposioHQ A curated list of awesome Claude Skills, resources, and tools for customizing Claude AI workflows 78.9k stars
• marketingskillsby coreyhaines31 Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, and growth engineering. 58.7k stars · 30 skills
• awesome-gamedev-agent-skillsby gamedev-skills 77 game-dev skills for AI coding agents — Godot, Unity, Unreal, Phaser, PixiJS, three.js, Bevy, pygame, LÖVE, Roblox. Portable SKILL.md Age… 6.9k stars
• graphifyby Graphify-Labs Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Curs… 143k stars · 1 skill