Pull-request chat commands

Prefix every command with @codejackrabbit in a GitHub pull-request comment. GitLab notes support review commands. @codejackrabbit help posts the same table in the thread.

Review control

CommandResult
reviewIncremental review using previous state
full reviewComplete review
pause / resumeStop or restart automatic reviews for this PR
ignore in the PR descriptionDisable reviews for this PR
summary in the PR descriptionPlaceholder replaced in place

Generation and repair

CommandResult
generate docstringsCreates a docstring patch task from PR files
generate unit testsCreates executable generated tests in a task
generate sequence diagramPosts a Mermaid diagram of changed areas
generate project vocabularyPosts project-specific terms
fix comments [stacked pr]Creates a fix task from stored findings and PR files
`autopilot [resume\stop]`Continuous fix-task creation after reviews
fix-ci [commit]Reads failed check runs, then creates a scoped task
resolve merge conflictCreates a conflict task from current PR files
local commitDirects the prepared task delivery through code push

Task replies report the actual task status. A task that cannot produce a valid patch stops at needs_attention with the blocker instead of being described as complete.

Management and information

CommandResult
approveResolve own threads, then approve only in request-changes workflow
resolveResolve CodeJackRabbit review threads repeatably
rate limitStored server usage and hourly key quota
configurationResolved JSON configuration
generate configurationReady-to-commit YAML configuration
emit path instructionsYAML suggested from stored learnings
learningsStored review preferences
helpFull command table

A reply to an existing review thread can install explicit feedback as a learning even without a command. Example: “stop flagging TODO in scripts/**” creates a scoped suppression. Other chat text is not treated as an implementation unless it matches a supported command.