Skip to content
axintdocs

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.

The short version: Axint should never make a developer paste a noisy console dump into an agent and hope the next run understands what happened. A failed check becomes a verdict, top findings, a next step, and a prompt the agent can use.

What Axint writes

Section titled “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 result
    • pass / needs review / fail
    • 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

Section titled “What is inside the Fix Packet”

The full packet includes:

  • result: pass, needs review, or fail
  • top findings and full diagnostics
  • confidence and status for every finding
  • evidence provenance, including supporting or contradictory Xcode proof
  • explicit blocking behavior
  • next steps
  • the AI repair prompt
  • generated artifact paths for Swift / plist / entitlements when available

Suppressed findings remain in the packet with their original severity and the evidence that removed them from the current gate. Consumers should not infer blocking behavior from severity alone.

The public explanation lives at axint.ai/fix-packet. Use that page when you need to show the artifact to a teammate or technical reviewer without sending them straight into repository docs.

MCP and AI usage

Section titled “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

Section titled “Xcode usage”

For Xcode-facing loops:

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

Use axint xcode check first when you only need the latest result and top finding.

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

Section titled “When to hand the packet to an AI”

The best flow is:

  • read the result
  • 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.

Section titled “Related docs”