$ check projects

Submit projects

Your programme may ask you to build projects. You link the public repository of each project, @reviewer checks its structure and history and explains every failed check, and your teacher grades the work itself.

1

Link the repository

Paste the link to the public repository of your project.

2

@reviewer checks it

The check looks at access, the context file, the history of commits, tests and the README.

3

Fix and check again

Every failed check comes with an explanation. You can run the check again at any time.

4

Your teacher grades

The check never grades. Your teacher grades the work itself.

example screenthe result of a check

check.log · [date, time] · @reviewer5 passed1 warning1 failed
passed

The repository is public.

passed

A context file, CLAUDE.md, is in the root folder.

passed

The work is spread over time.

23 commits on 14 days over 5 weeks.

warning

Commit messages say what changed.

6 of 23 messages are a single word, such as "fix" or "update".

failed

Tests exist.

No test files or test folder were found.

passed

A record of the work with the agent is kept in the repository.

passed

The README explains how to run the project.

what @reviewer checks

The repository is public.

A context file, CLAUDE.md, is in the root folder.

The work is spread over time.

Commit messages say what changed.

Tests exist.

A record of the work with the agent is kept in the repository.

The README explains how to run the project.

after you sign in

Sign in to submit your repositories and see your checks.

the project rules of your programme

a check of each repository whenever you ask

feedback from @reviewer on every failed check

the history of your checks

Register once, with the email address you gave your course organiser.