God Skills

Seven Claude Code skills. One team.

God Skills is seven open-source skills for Claude Code that work like a small company. One decides, one builds, one tests, one checks the money, one asks why, one writes, one watches your hours. Every run ends in a pull request that passed review, with the proof attached.

npx god-skills

MIT · zero dependencies · Node 18+

Why I built God Skills

I’m a senior product manager at SaffronStays and I ship code across several side projects. Claude Code made me fast, but the speed had a bill. Pull requests kept failing the auto-reviewer. Deploys dragged. After a long session I could not say what had actually changed. Deciding what to build, or whether to build it at all, was still on me. And the numbers: every revenue figure it touched, I re-checked by hand.

God Skills is how I fixed that. Each job went to a specialist with its own rules, its own checks, and a memory of what went wrong last time.

The seven Claude Code skills

Each owns one question and hands work to the next. Pick one.

god-ceo

Decides

What is the real problem, is it worth doing, who does it, and what is the final call?

  • Reconstructs the real problem before anyone codes, reading the codebase, not the ticket.
  • Ranks it against this week's priorities and says no to low-value work.
  • Routes the shortest chain of skills, attacks the plan, then calls it: BUILD, SHIP, DEFER or STOP.
  • Writes the decision and the why down, so “why does this exist” has an answer later.
Fires
when the ask is vague, spans two or more skills, or any skill is stuck
Returns
a one-screen decision memo

How a request flows through God Skills

From a sentence to a production-grade pull request, every time.

  1. You ask, in plain words.

    “Refunds are off by a rupee.” “Add CSV export.” “Should we build this?” No prompt engineering.

  2. god-ceo frames it, when the ask is vague or crosses skills.

    Reads the code, finds the real problem, decides if it is worth doing this week, picks the shortest chain. A clear single ask skips this step.

  3. god-dev plans, then builds.

    Picks small, normal or deep. Syncs git, checks for a branch already doing it, lists what could go wrong, removes before it adds, and writes to the auto-reviewer’s checklist so the PR passes first time.

  4. god-qa proves it.

    Runs the tests for real: backend, four screen sizes, keyboard, slow network, security when auth or input is touched. Scores every issue 1 to 5 and fixes up to three rounds. No PASS without proof.

  5. Specialists check their part.

    god-cfo recomputes any money a second way. god-cmo writes the PR body so a person can read it.

  6. You get a pull request that is ready to merge.

    Title with your deploy token. Body with problem, approach, rollback and test evidence. A test-cases doc, a manual guide, a change-log flowchart. The lesson saved for next time. One line from god-ally on your pace.

If god-qa fails it, god-dev fixes from the scored list and god-qa reruns, three times at most. Stuck anywhere, god-ceo steps in.

Try the router

Type a request. Watch who fires, in what order, and what you get back.

  1. god-devdeep mode

    Touches money, data or auth, so it designs first, then builds to the reviewer's checklist.

  2. god-qa

    Runs the tests itself, four screen sizes if there is UI. Nothing is done until it returns PASS.

  3. god-cfo

    Recomputes every number a second way before it is trusted.

  4. god-ally

    Closes the reply with today’s pace. One line, only when it has something to say.

  5. You get

    A pull request with problem, approach, rollback and test evidence, god-qa’s verdict, a test-cases doc and a manual guide. Signed 🥷🏾 Authored by God.

A sketch of the real auto-trigger rules, matched on words. The skills read the whole request.

What you get out of the box

Agents and hooks

A skill is knowledge in your session. god-agents turns each one into a subagent with its own context window, tool allowlist and model, and adds the part a prompt cannot talk its way out of: hooks.

Agents are opt-in. By default every skill runs inline, in your session, where you can watch it work.

Install God Skills

npx god-skills           # every skill, asks global or project
npx god-skills list      # see the seven
npx god-skills doctor    # verify the install
npx god-agents --all     # subagents, /god, and the hook gates

Restart Claude Code after installing. Skills load at session start.

Other CLIs read the same Markdown:

npx god-skills --codex                             # ./AGENTS.md
npx god-skills --gemini                            # ./GEMINI.md
npx god-skills --agents-md .cursor/rules/god.md    # any instruction file

Frequently asked questions

What is God Skills?
God Skills is a free, open-source set of seven skills for Claude Code that work like a small company: god-ceo decides, god-dev builds, god-qa proves, god-cfo counts, god-pm asks why, god-cmo writes and god-ally watches your pace. Each run ends in a tested, reviewed pull request instead of a guess.
What is a Claude Code skill?
A skill is a Markdown file that Claude Code loads at the start of a session and follows for one kind of job. God Skills ships seven that hand work to each other and share one learning loop.
How do I install God Skills?
Run npx god-skills, choose global or project, and restart Claude Code. npx god-agents --all adds subagents, the /god command and the hook gates. Node 18 or newer, no other dependencies.
Does it work with Codex, Gemini CLI or Cursor?
Yes. npx god-skills --codex writes AGENTS.md, --gemini writes GEMINI.md, and --agents-md <file> targets any instruction file. The hook gates are a Claude Code feature and do not port.
What does god-qa actually test?
It runs the tests itself: backend and logic, the UI at 390, 820, 1512 and 1440 pixels, keyboard and screen reader, slow network, a security pass when the diff touches auth or input, and a DPDP and ISO 27001 pass when it touches personal data. Every issue is scored 1 to 5. A test that could not run is reported UNVERIFIED, never PASS.
What leaves my machine?
Nothing, except a summarized universal lesson that opens as a pull request to the skills repo, which you can turn off. Lessons, decisions, scorecards and the activity log stay in ~/.claude/god/.
Is God Skills free?
Yes. MIT licensed, zero dependencies, source on GitHub, packages god-skills and god-agents on npm.