Jern Cloud docs

Recipes.

Each recipe is a policy, a message or a schedule, and what came back: a real pull request on the public demo repository with its receipt, where one exists. Copy the policy, change the message, and the shape of the result is the same on your repository.

Look for bugs every TuesdayA scheduled session reviews the code, fixes what it finds within a blast radius, runs the tests, and opens a pull request. A real run on the demo repository, with its receipt.Add docstrings the way this repository writes themA skill under .jern/skills tells the agent how a docstring is written here. Asked to add missing ones, it reads the skill and follows it, and leaves the rest alone. A real session with its receipt.Turn an issue into a pull request with a labelPut the jern label on an issue and a session opens with the issue as its task, as the person who labelled it. A real session from the demo repository, with its receipt.Update the dependencies every MondayA schedule, a message, and a baseline that lets the agent change lockfiles and run the tests. The recipe most teams ask for first; the demo repository has no dependencies, so this one has no run to show yet.

The demo repository is jern-ai/jern-demo: a small Python project with a deliberate bug, a protected baseline, and a skill. Every pull request the sessions opened is still there with its Jern receipt check.