Extension
Sign in
Install App (opens in a new tab)

Docs & Rules

yegor256/quliceGitHub

This is a public, read-only report. Striff reads this repository's docs, turns each sentence that makes a claim about the code into a rule, and checks the rule against the code on the default branch. How this works

master752c4e7Last refreshed 7h ago

Is this yours? Install to manage it

Once installed, Striff checks every pull request.

5
5
1 doc
yegor256/quliceOpen repository

yegor256/qulice — documented rules

5 of 5 rules, printed October 8, 2026.

The sentence in your docs
Read Oct 7
Validator consumes the full Environment for checks that require broader project context.
Validator depends on Environment
Holds
Read Oct 7
The com.qulice.checkstyle package contains roughly forty custom AbstractCheck implementations (e.g., ConstructorsOrderCheck, IfThenThrowElseCheck) covering constraints absent from the standard [Checkstyle] catalog.
ConstructorsOrderCheck is in com.qulice.checkstyle
Holds
Read Oct 7
The com.qulice.checkstyle package contains roughly forty custom AbstractCheck implementations (e.g., ConstructorsOrderCheck, IfThenThrowElseCheck) covering constraints absent from the standard [Checkstyle] catalog.
IfThenThrowElseCheck is in com.qulice.checkstyle
Holds
Read Oct 7
The com.qulice.pmd.rules package adds custom AbstractJavaRule implementations (e.g., UnitTestContainsTooManyAssertsRule, ProhibitPlainJunitAssertionsRule) that replace upstream [PMD] rules with known false-positive defects filed in the upstream tracker.
UnitTestContainsTooManyAssertsRule is in com.qulice.pmd.rules
Holds
Read Oct 7
The com.qulice.pmd.rules package adds custom AbstractJavaRule implementations (e.g., UnitTestContainsTooManyAssertsRule, ProhibitPlainJunitAssertionsRule) that replace upstream [PMD] rules with known false-positive defects filed in the upstream tracker.
ProhibitPlainJunitAssertionsRule is in com.qulice.pmd.rules
Holds
5 rules from 1 doc

See these where the change is. The browser extension puts a pull request's doc findings, and a diagram of what it changed, on the GitHub page itself, so the code and what your docs say about it are side by side.