record_fix
Records a confirmed fix and closes the related or active issue once tests pass or the user confirms, updating project memory.
Instructions
Record a confirmed fix and close an issue.
Only call AFTER you have evidence the fix works: test passes, error is gone,
or the user confirmed.
If `issue_id` is provided, the fix is attached to that specific issue.
If `issue_id` is omitted, the active issue is closed.
Side effects: appends a `fix` event and updates summary.md. The active-issue
marker is cleared only when the active issue is the issue being fixed.Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"summary": "<summary>"
},
"name": "record_fix"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project | No | Which project this call is about — a registered id, alias, or absolute path (e.g. 'ossdrop'). Omit it when the server was started for a single repo, or when an active project is set with `pjm project use`. Call list_projects to see the registered names. | |
| summary | Yes | One-line description of the confirmed fix (e.g., 'guarded submit handler with isSubmitting ref'). Keep it under 300 characters. | |
| issue_id | No | Optional zero-padded issue ID (e.g., '0042') to close. When omitted, closes the active issue. Numeric strings without padding are accepted. | |
| location | No | Optional file path or component where the fix was applied. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |