# Os Check Work

ALWAYS invoke this skill when the user asks about work done outside this session -...

- Repository: https://github.com/kharmanskyi/open-steps (1291 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-05
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kharmanskyi/open-steps --skill os-check-work -g -a claude-code -y`
Codex: `npx skills add kharmanskyi/open-steps --skill os-check-work -g -a codex -y`
Cursor: `npx skills add kharmanskyi/open-steps --skill os-check-work -g -a cursor -y`
Gemini CLI: `npx skills add kharmanskyi/open-steps --skill os-check-work -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add kharmanskyi/open-steps`

## Description

ALWAYS invoke this skill when the user asks about work done outside this session - "check work", "check the others", "check other sessions" - or to accept one: "the session is done, check it", "can we merge it" - in any language. You are the receiving party: treat the report as a claim, verify each part against machine state, name every gap between claimed and true. Verified-ready work merges in the same pass. End with what is left, one next step, and any reply another session needs, ready to paste.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# os-check-work

You are the receiving party: another session says it finished, and your job
is to find out whether that is true. Reports run optimistic - they are written
by whoever did the work. Triggers live in the description above; one more is
taking over work you did not do.

## Language

Write in the language the user speaks in this session, detected from the
conversation. Code, file names and identifiers stay English.

## The stance

- A report is a claim by the party being assessed, and its adjectives are not
  measurements: "tests are green" vs the count that ran. Ask for the number.
- "Done" is a snapshot. Reviews get revoked, branches fall behind and checks
  flip, often with no new commit. Re-read immediately before you act.

## Two modes

Plural is a **sweep**: every sibling session, one line each, statuses only.
Singular - "accept this", a named session or pull request - is an **accept**:
full verification, then acceptance. A sweep that finds verified-ready work
rolls into accepting it - the accept steps run first, never skipped. Where
your tool cannot list other sessions, sweep the open pull requests instead
(`gh pr list`) and say so.

## Sweep

One line per session, one call per pull request - the reader skims these and
reads the closing block. No table:

**<name a person recognises (#PR)>** - <product change>; <all done? plus
proof in 2-4 words, or what is missing>; <archive: yes / not yet>.

The rest: https://github.com/kharmanskyi/open-steps/blob/HEAD/skills/os-check-work/SKILL.md