duplicate-rule

Severity: warning in one section or a block copied under the same heading; a note under unrelated headings; nothing for parallel sibling sections.

What it catches#

The same rule appears twice in one file.

The same instruction written twice in one file. Comparison ignores case, list markers, emphasis, backticks and a leading "a", "an" or "the", and joins wrapped lines first, so a rule and its rewrap still match. Short labels that repeat as structure ("Checklist"), bold labels and template lines that are mostly placeholders ("- [Finding] -> [why]") are not counted, and a paragraph gives at most one finding.

Where the two copies sit decides what is reported. In one section, or in a block of text copied from a section with the same heading, it is a warning. Under two unrelated headings it is a note, because a summary section and its detail often repeat a rule on purpose. Under parallel sibling headings or labels (Regular posts and Video posts, Phase 1 and Phase 3, "If using artifacts" and "If using a file") it is not reported: two procedures share steps by design. An AGENTS.md inside a skill, template or example folder is reference material and is not checked.

Why it matters#

Duplicates cost context and drift apart when only one copy is edited. Two procedures or variants side by side (Regular posts and Video posts, Phase 1 and Phase 3) share steps on purpose, so those are not reported.

## Workflow

- Run `npm test` before every commit.
- Keep commit messages under 72 characters.

## Before you push

- Run `npm test` before every commit.
- Rebase on main.

## Workflow

- Run `npm test` before every commit.
- Keep commit messages under 72 characters.
- Rebase on main before you push.

How to fix#

Delete one copy. If the two sections describe alternatives that never apply together (a release path and a hotfix path, each listing the same step), suppress the finding with a comment that says so.

Suppress or configure#

For one finding, put a comment on the line above it. The reason after -- is optional but worth writing:

<!-- asitis-disable-next-line duplicate-rule -- why this one is fine -->

For a whole file:

<!-- asitis-disable-file duplicate-rule -- why this file is an exception -->

For every file, turn it off or change its severity in .asitisrc.json:

{ "rules": { "duplicate-rule": "off" } }

A .asitisrc.json overrides entry limits a change to some paths, and a baseline (asitis lint --format json --write-baseline) accepts today's findings so only new ones fail the build.

Source#

Claude Code docs: How Claude remembers your project, read on 14 October 2026.