Skip to content
Axint

Fix Packets

Fix Packets are Axint’s repair contract.

They exist so your AI tool, your CLI flow, and your Xcode workflow can all read the same repair artifact instead of inventing different diagnostics formats for every surface.

What Axint writes

Every compile, watch, and validate-swift run writes:

.axint/fix/latest.check.json
.axint/fix/latest.check.md
.axint/fix/latest.json
.axint/fix/latest.md

The split is intentional:

  • latest.check.*

    • quick verdict
    • top findings
    • next step

  • latest.*

    • full Fix Packet
    • full diagnostics
    • AI-ready repair brief
    • Xcode checklist
    • generated artifact hints

What is inside the Fix Packet

The full packet includes:

  • verdict: pass, needs review, or fail
  • top findings and full diagnostics
  • confidence level
  • next steps
  • the AI repair prompt
  • generated artifact paths for Swift / plist / entitlements when available

MCP and AI usage

If your AI client is using MCP, it can read the latest packet through:

  • axint.fix-packet

Formats:

  • json
  • markdown
  • prompt

That means the AI loop can be:

  1. user runs Axint
  2. Axint emits the local packet
  3. AI client reads the packet directly
  4. AI applies the repair
  5. user reruns Axint

Xcode usage

For Xcode-facing loops:

Terminal window
axint xcode check
axint xcode packet --format prompt

Use check first when you only need the quick verdict.

Open the packet when you want:

  • the detailed repair prompt
  • the full Apple findings
  • the richer checklist

When to hand the packet to an AI

The best flow is:

  • read the verdict
  • decide if you need the full repair brief
  • copy the prompt when you do

That keeps the human experience simple while still giving AI tools all the detail they need.