ahmedessameldeen

Orbits Check — Development skill for Claude Code

Development community

Close the orbit — re-run the baseline query weeks after a fix shipped and find out whether the number actually moved.

How to install Orbits Check

Installs to ~/.claude/skills/ahmedessameldeen-orbits-orbits-check/SKILL.md

Terminal
mkdir -p ~/.claude/skills/ahmedessameldeen-orbits-orbits-check && curl -fsSL https://raw.githubusercontent.com/ahmedessameldeen/orbits/HEAD/commands/orbits-check.md -o ~/.claude/skills/ahmedessameldeen-orbits-orbits-check/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Orbits Check does


name: orbits-check description: Close the orbit — re-run the baseline query weeks after a fix shipped and find out whether the number actually moved. The step almost every team skips. argument-hint: ""

/orbits-check

Close the orbit on: $ARGUMENTS

**A merged pull request is a claim, not evidence.** The evidence arrives weeks later, in the data.

How to run it

Load the `orbits` skill and read `references/metrics.md`.

  1. **Find the

Alternatives in Development

  • Content Shipped — Proactively detect and log shipped content when user mentions publishing, launching, or completing work 1k ★
  • Quick Eval — Quick job evaluation 473 ★
  • Migrations — Versioned breaking change migrations for Turbo 263 ★

Full documentation available on GitHub

View Source Repository