mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00

Files

T

Renn F f48106cbb6 docs: reflow hard-wrapped prose to one line per paragraph

Markdown and editors soft-wrap on their own, so the manual ~75-char line
breaks across the docs added nothing but noise. Join wrapped prose, list
items, and paragraphs into single lines across 67 docs — README, CLAUDE.md,
deployment, usage, the RAG knowledge base, and the agent role prompts.
Whitespace-only: code fences, tables, and blockquote alerts are byte-identical
and the change is token-verified (no content altered). Applied with a
deterministic reflow tool (committed separately).

Also lands two doc edits that were awaiting commit: the measured under-load
resource numbers in usage.md and the pr_reviewer additions to the
org-structure RAG doc.

2026-06-16 23:18:55 +02:00

2.2 KiB

Raw Blame History

Git Commit Workflow

Commit Format

All commits are automatically prefixed with the task ID by the choreographer:

[{task-id-prefix}] {message}

Example: [a1b2c3d4] Add rate limiting endpoint

You write the message — the prefix is added for you. Don't include [task-id] yourself; it gets stripped and re-applied.

Who Can Commit

commit is in the roboco-do MCP and is mounted only for developers and documenters. PMs delegate code work and call complete to merge.

There is no roboco_git_commit / _push / _create_pr MCP tool. The single commit verb covers commit + push + PR-trigger via the choreographer.

Creating Commits

commit(
    message="Add rate limiting endpoint",
    files=["roboco/api/routes/rate.py"],  # optional; defaults to all staged
)

This automatically:

Prefixes the commit with [task-id-first-8-chars]
Validates the message via commit_validator
Stages the listed files (or everything tracked + modified if omitted)
Pushes to the agent's auto-created branch
Records the commit on the task (commits[] field on TaskTable)
Opens a PR through the choreographer when the task transitions out of in_progress (no separate create_pr call required)

Before Committing

Run tests: uv run pytest or pnpm test
Run linter: uv run ruff check . or pnpm lint
Run type check: uv run mypy roboco/ or pnpm typecheck
Format code: uv run ruff format . or pnpm format

After Committing

You don't push or create a PR yourself. The choreographer pushed the commit during commit(), and the PR is opened/merged as part of the lifecycle transitions:

open_pr(task_id) — opens the PR (devs)
pass(task_id) (QA) → i_documented(task_id) (doc) → complete(task_id) (cell PM merges the leaf PR; main PM opens the master PR)

Viewing Commits and History

# Read-only inspection (any role) — roboco-git-readonly MCP
status = roboco_git_status(project_slug="roboco")
log = roboco_git_log(project_slug="roboco", branch="feature/backend/a1b2c3d4--def67890")
diff = roboco_git_diff(project_slug="roboco")
branches = roboco_git_branch_list(project_slug="roboco")

2.2 KiB Raw Blame History