explaingit

zaxardery8011-design/soplint

Analysis updated 2026-05-18

39PowerShellAudience · developerComplexity · 3/5LicenseSetup · moderate

TLDR

A linter that checks whether your AI agent actually keeps the working agreements you made with it, not whether its code style is clean.

Mindmap

mindmap
  root((soplint))
    What it does
      Lints agent discipline
      Belief revision audit trail
      Pre-action command gate
    Tech stack
      PowerShell
      JSON
      CI CD
    Use cases
      Track belief reversals
      Catch stale memory decisions
      Block risky shell commands
    Audience
      Developers running AI agents

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Log every time an AI agent reverses a prior judgment so the pattern is visible in a greppable audit trail.

USE CASE 2

Run daily discipline checks in CI that catch decisions logged in memory but never propagated to the agent's instructions.

USE CASE 3

Block an agent from running risky shell commands with a pre-action hook backed by hard deny rules.

USE CASE 4

Require an agent to prove it checked for an existing tool before building a new one.

What is it built with?

PowerShellJSONCI/CD

How does it compare?

zaxardery8011-design/soplintsbousseaden/edrunchokerzy-zmc/tianming-skill
Stars393527
LanguagePowerShellPowerShellPowerShell
Setup difficultymoderatemoderatehard
Complexity3/53/53/5
Audiencedeveloperops devopswriter

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires PowerShell 7+ and manual configuration of memory_dir, claude_md_path, and log file paths before first run.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

soplint is a linting tool built not to check your code style but to check whether your AI agent actually keeps the agreements you made with it. The author spent a year running a personal AI agent continuously and found that code quality was rarely the issue. The real problems were behavioral: the agent would say it had verified something without verifying it, quietly reverse decisions it had just made, or learn a new rule in one session and drift back to old behavior in the next. The tool addresses this with three mechanisms. The first is a belief revision audit trail. Whenever the agent changes its mind about something it previously stated, it must write a structured log entry recording what it believed before, what it believes now, and why it changed. This gives you a greppable file of every time the agent reversed a judgment, which is much harder to hide than simply ignoring a rule written in a prompt. The second mechanism is a set of daily discipline checks run as a script. These checks scan your agent's memory files and instruction documents for specific failure patterns: a decision that was logged in a memory file but never propagated to the agent's main instructions file, a belief log that is not being written at all, memory files missing required metadata, and a memory index that has grown so large or cluttered that the agent cannot actually load all of it during a session. Each check exits with a non-zero code on failure so it can plug into a CI pipeline or a scheduled job. The third mechanism is a pre-action gate that runs as a hook before the agent executes shell commands. It parses the command using PowerShell's built-in syntax tree tools and applies two kinds of rules from an external JSON file: hard deny rules that block specific commands outright, and novelty gates that require the agent to confirm it checked for an existing tool before building a new one. The README is explicit that this is not an alignment solution. It is a regression test suite for known failure modes, each check backed by a real incident. The author's framing is that a lesson written to memory is a hope, but a lesson with a lint rule becomes a regression signal you can run every day. Requires PowerShell 7 and runs on Linux, macOS, and Windows.

Copy-paste prompts

Prompt 1
Help me set up soplint in my repo so my Claude Code agent logs every belief revision it makes.
Prompt 2
Explain how soplint's decision_propagation check catches memory decisions that never made it into CLAUDE.md.
Prompt 3
Walk me through writing a deny rule and a novelty gate in guard-rules.example.json for my agent's pre-action hook.
Prompt 4
Show me how to wire soplint's discipline checks into a CI pipeline so failures block a merge.

Frequently asked questions

What is soplint?

A linter that checks whether your AI agent actually keeps the working agreements you made with it, not whether its code style is clean.

What language is soplint written in?

Mainly PowerShell. The stack also includes PowerShell, JSON, CI/CD.

What license does soplint use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is soplint to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is soplint for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.