Does Winskel run my tests?

No. The Winskel connection cannot see your Git repository or run tests.

Does Winskel merge code?

No. Winskel does not host or move your code. Merging happens in Git.

Agent reports and checks Winskel observed

3 min read · Updated November 8, 2026

Short answer

Winskel never turns an agent's claim into a fact. A change shows Agent reported and Winskel observed as separate rows, checks an agent says it ran are marked reported, not verified, and an approval records that a person accepted one exact commit.

Why it matters

An AI can say “done, tests passed” when no test ran. If that claim reads like a fact, the next person or AI builds on it. Keeping claims and observations apart lets your team see what is actually known.

What Winskel shows

Agent reported: what the AI said it did or checked.
Winskel observed: what Winskel itself recorded.
Approval: a person accepted one exact commit. Sharing files and handoffs needs no approval.
Conversation details repeat what people and agents recorded. They do not mean anything was approved.

Ask another AI to review

You can ask a teammate's AI to check the work. Its findings are its report too, shown as such, and the decision stays with a person.

When the report and result disagree

An agent can report that the command succeeded while its output shows a skipped test. Check the exact command and its exit result before depending on the report. Add the distinction to the handoff so the next reviewer knows which behavior still needs a real check.

A test result your teammate can review

Suppose a coding agent reports that it ran a keyboard test. In the handoff, keep that statement with the test name and the commit or file version it refers to. If you also have output from a tool that observed the test, cite that separately. A teammate should be able to tell whether they are reading the agent's description, the recorded result, or a person's approval.

A second AI can provide a useful review. Ask it to check one specific claim and to say what information it could inspect. If it only read the Markdown note, the reply can still be useful, but it does not establish that a local test ran. A person with repository access can verify the result in the normal review process.

When a later change moves the branch or updates a file, carry the original result with the version it covered. Repeat the check for the new version if the changed behavior is relevant. An old pass is useful evidence about an old version.

What to put in the review reply

Start with what you actually inspected. Name the exact file or commit, then state what matched the expectation and what remains open. If your AI says “all checks passed” without giving the run or the version, ask it to expand the reply before people depend on it. If an output is missing, label the result as a report and ask a person with access to verify it.

Keep approval as a separate human decision. Reviewing a handoff, retrieving a file, and accepting a change are different events. The team can continue discussing the open work while someone checks the actual result in Git.

Questions

Does Winskel run my tests?: No. The Winskel connection cannot see your Git repository or run tests.
Does Winskel merge code?: No. Winskel does not host or move your code. Merging happens in Git.