Skip to content

AI_INSTRUCTIONS.md mentions precheck_file(path) when the key argument is actually file_path #18

Description

@medium-effort

copying from AI_INSTRUCTIONS.md

2. **Call `precheck_file(path)`** (MCP) or `pjm precheck <path>` (CLI) — MANDATORY before proposing ANY change to a file. It surfaces that file's failed past approaches, open issues, and churn in ~100 tokens, so you never re-try a known dead-end.

meanwhile when i check the precheck_file.json of the mcp.

{
  "name": "precheck_file",
  "description": "Check a file's failure history BEFORE modifying it.\n\n    MANDATORY: call this BEFORE proposing any change to a file.\n    Surfaces failed past approaches, unresolved issues, and high churn\n    so you don't repeat known dead-ends. Cheap (~100 tokens) and prevents\n    expensive re-debugging cycles.\n\n    Read-only; does not modify memory.",
  "parameters": {
    "properties": {
      "file_path": {
        "description": "Project-relative or absolute file path to check (e.g., 'src/auth.py'). Matched against the `location` field of logged events — no file content is read from disk. Returns 'no warnings' if the file has no failure history.",
        "title": "File Path",
        "type": "string"
      },

My agent does this mistake a lot because of the wrong instruction.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions