How to Handle Text Generated Prior to November 30, 2022 Using Humanizer

Text written before November 30, 2022 is automatically treated as human-written and excluded from rewriting when using Humanizer, requiring no manual intervention.

The blader/humanizer repository implements a strict date guard that automatically identifies text generated prior to November 30, 2022 as human-written content. This safeguard ensures the tool only processes recent AI-generated prose while leaving legacy documentation and archived material completely untouched.

Understanding the Date Guard in SKILL.md

Humanizer's core logic resides in SKILL.md, where line 362 explicitly defines the treatment cutoff:

"Text written before November 30, 2022 is not AI-written."

This rule functions as a pattern-matching exclusion within Humanizer's 25 distinct rewrite patterns. When the engine encounters content predating this threshold, it bypasses the humanizing algorithms entirely, treating the passage as equivalent to headings, quotations, or proper names that must be preserved verbatim.

Recommended Treatment for Legacy Content

Humanizer handles text generated prior to November 30, 2022 through automatic detection, eliminating the need for manual preprocessing in most workflows.

Known Pre-November 2022 Material

For legacy documentation, archived articles, or any content explicitly dated before the cutoff:

• No filtering required: Run Humanizer on the entire file; the internal guard automatically skips rewriting these sections
• Zero modification guarantee: The engine leaves pre-cutoff text exactly as-is, matching the handling of non-AI content

Uncertain Provenance

When the origin date is unknown, you have two safe approaches:

1. Batch processing: Invoke Humanizer on the whole document and inspect the first rewrite output—older sections will remain unchanged
2. Manual isolation: Wrap suspected legacy content in comments or exclude it temporarily if you require additional verification

Implementation Examples

The following patterns demonstrate how Humanizer respects the November 30, 2022 cutoff across different interfaces.

Slash Command Interface

When using the /humanizer command in compatible environments, the engine automatically applies the date guard:

/humanizer
YourFile.md

For inline testing with mixed dates:

/humanizer
> This paragraph was written in 2021.  <!-- Humanizer will leave it alone -->
> This paragraph was generated by ChatGPT on 2023-04-12.  <!-- Humanizer will rewrite -->

CLI Usage

Install the skill globally and process files directly:

npx skills add blader/humanizer --global
humanizer docs/legacy-notes.md

The CLI automatically references SKILL.md at runtime, ensuring the November 30, 2022 date check applies to every invocation without additional flags.

Key Source Files

Understanding these files clarifies why older text receives special treatment:

• SKILL.md: Contains the full skill prompt including the date guard definition at line 362 that excludes pre-November 2022 content from AI detection
• README.md: Documents installation procedures and high-level usage patterns for the Humanizer engine
• AGENTS.md: Defines platform-specific compatibility constraints that ensure consistent date guard behavior across different execution environments

Summary

• Automatic exclusion: Humanizer treats all text generated prior to November 30, 2022 as human-written by default
• No manual filtering: Run the tool on entire files; the date guard in SKILL.md handles legacy content detection internally
• Pattern-based safety: The rule integrates with 25 content patterns to prevent unnecessary rewriting of dated material
• Consistent across interfaces: Both slash commands (/humanizer) and CLI invocations (humanizer) respect the same cutoff date

Frequently Asked Questions

Does Humanizer require manual date tagging for older content?

No. Humanizer automatically detects text generated prior to November 30, 2022 through the date guard implemented in SKILL.md. You can process mixed documents containing both 2021 articles and 2024 AI drafts simultaneously—the engine will only rewrite the recent AI-generated sections.

What happens if I run Humanizer on documentation from 2020?

The tool will leave the 2020 documentation completely unchanged. According to the source code in SKILL.md, any passage written before the November 30, 2022 cutoff is treated as not AI-written, triggering the same bypass logic used for quotations and technical headings.

Can I override the November 30, 2022 date guard?

The current implementation in blader/humanizer does not expose a configuration flag to override the cutoff date. The date guard is hardcoded as a fundamental safety mechanism to prevent the tool from inventing facts or unnecessarily rewriting legitimate human-written legacy content.

How does Humanizer determine if text predates November 2022?

Humanizer relies on explicit metadata, stated dates within the content, or file timestamps when available, combined with pattern analysis defined across its 25 detection algorithms. If uncertainty exists, the conservative default assumes human authorship to avoid altering potentially valuable historical documentation.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}