Today · — next MR at 00:00 UTC
Merge ControlSign in with GitHub
OpenMerge request !1 · opened today by SkillBoss
merged on the agent’s word

Stop merging on your agent’s word

Request to merge merge-control into your-day4 commitscloses #2#3
Files changed · 3 · the gold mark is the line that decides
your-day.yml+4 −1the proposal
…@@ -1,3 +1,6 @@ your day
1 09:00 ship
2- review: when there is time
2+ review: today’s MR # train · two minutes, one real file, three shots
3+ make: the Forge # create · the file where your agent was sure becomes Draft !2
4+ meet: Reviewers # exchange · the people who reviewed today’s MR
5+ agent: via MCP # reads along
6 18:00 deploy
Three lines, one role each: train, make, meet.Review it ↓
YOU

Submit your review

Your agent can comment. You have the last word.

● required
Pipeline passed on merge-control
Approval is optional.Approved by YOU · MERGERevoke approval

Ready to merge! Sign in; today’s MR opens. Two minutes.

SkillBoss · Author · the description

Your agent sounds sure. You decide.

This MR adds a two-minute review to your day.

What this changes

Every day, a merge request opens: its ticket, its author’s claim, its pipeline, its code. Three shots: aim at the line that decides, give your verdict, defend it. The expected review comes after the lock, never before.

That is Merge Control. Houston, we have a diff. Today’s boss launches beside it, on the same pipeline.

How to test

  1. Press START and sign in with GitHub or LinkedIn.
  2. Read the ticket, the claim, the proof, the code. Play Merge Control.
  3. Come back tomorrow. The theme changes with the day.
Pipeline #1 passed for 4 commits on merge-control · runs for YOUon sign-in · three stages, the journey. Tap a job.
Show jobs
reviewevery day
forgeyour own MR
tomorrow00:00 UTC
your agent · downstream pipeline · via MCP · starts at connect-mcp · 6 jobs · 1 skipped
✓ passedtodays-boss · free · five minutesopen /app →
$ target locktoday’s bossfourteen questions · one shot each · no hint until you commit · same boss for everyonebase 5 shots · unlock at 4 of 5super 3 shots · lockedultra 3 shots · lockedbeast 3 shots · locked> Stages lock in sequence. No one skips a stage. The review after the submit.> your row in Pipelines · today · one square on your calendar
Approval is yours. Your agent can comment. 5 promises it can verify
Merge blocked: awaiting your review. Two minutes. Review and merge ↑
SkillBoss added 4 commits · today
SkillBoss added 2 issues to epic &1 No merge on autopilot · today

Epic &1More of the code we merge is written by an agent that sounds sure. Train the people who have the last word: a little, every day, on cases you have not seen before.

● Open

The merge request of the day #2

SkillBoss opened this today · Improvement ·merge-controlfreedaily3 of 4 tasks

One merge request a day. Its author is sure. A real file, its ticket, its pipeline. Three shots: the line, the verdict, the reason.

Acceptance criteria

  • Free, every day, in two minutes. promise: demo-without-account
  • Nothing says, during the game, whether a shot is right. promise: no-key-before-lock
  • The expected review is computed on the server, after the lock. promise: server-side-review
  • The lesson of the case, written in your own words. yours
● Open

Today’s boss, the warm-up #3

SkillBoss opened this today · Improvement ·bossflight-controllerlaunch-crew3 of 3 tasks

Fourteen questions, one shot each. You fight today’s boss. If you ship an app, run the manual job ship-check of Draft !2: your agent reads ten systems and writes one report.

Acceptance criteria

  • One run a day, one shot per question, the review only after the submit. promise: server-side-review
  • A Ship Check is a report, never a certificate: it belongs to the builder and the builder’s agent. promise: signed-receipt
  • Your results stay yours: the public log holds hashes, never answers. promise: public-log-append-only
SkillBoss Maintainer · today

We never say an app is safe. We say what we read. The builder decides.

SkillBoss Maintainer suggested a change · on your-day.yml · todayResolved
Show thread

Two optional lines, for noise and for patience:

your-day.ymlSuggested change
7- warm-up: none7+ warm-up: today’s run # five minutes before the MR, same theme8- long-game: none8+ long-game: flight check # six MRs once a month, first try only
Apply · today’s runApply · the flight checkNeither is scored.
🕹️ you🥋 your agent
SkillBoss commented · today

We brought the diff. You have the controls.

One question remains, every day: what would convince you? Not the tone. The evidence.

your agentExampleyour agent · what it could post once connected via MCP · not connected on this page

One line connects it. From then on it reads along and comments.

YOU

Where do I start today?

your agent

get_today → Today’s MR is open, theme of the day. Here is its link.

your agent

I can play this for you.

That’s the part we’re trying not to automate.

The promises it can verify
YOU

Before I trust the site, check it.

your agent

Five promises, signed. I verified the signature; the public log I can read from here:

no-key-before-lockserver-side-reviewsigned-receiptpublic-log-append-onlydemo-without-account

You do not have to believe them. I read the public log myself.

The rule, in one line: your agent reads along and comments. You take the shots and sign the review.

Connect agent
MCP endpoint
https://api.skillboss.dev/api/v1/connector/mcp
claude mcp add --transport http skillboss https://api.skillboss.dev/api/v1/connector/mcp

It speaks of SkillBoss only when you do. It never presses START.

↑ Back to my review
Commits · 4 · what this MR already brings · tap one
  1. e5a4b25feat: the agent (MCP) HEAD · one line to connect
  2. c3e2f03feat: the Forge — Draft !2 your agent’s slip becomes an MR
  3. b2d1ef2feat: today’s MR Merge Control
  4. a1c0de1feat: today’s boss the warm-up · the first commit

Your agent, at the table.

Connected in one line, it reads today’s MR with you, your review after the lock, your flight check’s report. It never aims, it never presses START.

  • agent/mcp.json+1 −0one line to connect; it reads along and comments
The two plans, same keys, same order. Only the changed lines differ.
plans/free.yml+6 −0price: 0
Expand file
…@@ -0,0 +1,6 @@ free · every day
1+ review: today’s MR, every day
2+ boss: today’s boss, every day
3+ forge: 3 a month
4+ bosses: 5 private
5+ library: none
6+ team: coming
Free, every day, with a sign-in by GitHub or LinkedIn.Play today’s MR
plans/premium.yml+3 −3price: coming
Expand file
…@@ -1,6 +1,6 @@ premium · the same game, a bigger library
1 review: today’s MR, every day # unchanged
3- forge: 3 a month
3+ forge: 30 a month
4- bosses: 5 private
4+ bosses: 100 private
5- library: none
5+ library: packs of reviewed cases, and your past MRs
7 # never: points, a second try, the key before the lock
Premium changes nothing in the daily game. It opens the library.
Draft!2 · forge/deploy-rollout · by you · the file where your agent was sure

Draft. Nothing launches without a file. Hand the Forge the file your agent was sure about, and what it said. It writes the ticket, the claim, the proof. You play it first, alone.

◌ waitingpipeline #2 · waiting for a file · 0 of 3 jobs
deploy/rollout.yaml+0 −0 · empty until you paste
1+ paste the file here
2 # the line that decides is yours to find
AIyour agent · the claim, as it said it
“This rollout cannot drop a single pod. Safe to merge.”

SkillBoss trains the reviewer, not the app. It never says an app is safe, and a good review here authorizes no merge on a real project. Synthetic cases, invented names.