DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to block AI-tell copy from merging with a strict scan with Humanizer Stack

Use the scanner's exit codes and JSON output to fail a check when a draft still has copy tells.

  • Content
  • Advanced
  • 30 minutes
  • From the README
  • Any agent

Who it is forA developer or operations lead who keeps published copy in a repo and wants a repeatable check before changes are merged.

The problemWord-level tells slip into shared copy files during edits, and nobody runs the check by hand every time.

The outcomeA scan step that returns a nonzero exit code on any hit and produces machine-readable output for review tooling.

What you need first

  • Claude Code installed, since the passes are packaged as Claude Code Skills
  • git and a terminal to clone the repo and run install.sh
  • Python 3 to run the scanners
  • A draft file in plain text or Markdown to work on

Steps

  1. git clone https://github.com/NulightJens/humanizer-stack.git
  2. cd humanizer-stack
  3. python3 scripts/copy_scan.py --json draft.md
  4. python3 scripts/copy_scan.py --strict draft.md
  5. Add the --strict command to a pre-commit or CI step that runs on the copy files, and mark intentional usages with copy-ignore. (inferred, check the README)

Prompt for your agent

In the humanizer-stack repo at <repo path>, run python3 scripts/copy_scan.py --strict on <copy file> and capture the exit code and the output from --json. Report each hit with its line number and whether the file passed. Verify that a file with no hits returns exit code 0.

Caveat. The scanner is hook-friendly but only catches the pattern-matchable slice, so it cannot replace the judgment work in the skills.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page