A comment about the task or the change rather than the code: "as per the requirements", "previously this called X", "no longer needed". It records the conversation that produced the code.
Each example shows the exact code shape the rule is looking for, then the smallest version that keeps the intent without hiding risk or adding noise.
export async function listInvoices(cursor?: string) {
// Added pagination as per the requirements
// Previously this returned every row in one query
return db.invoice.findMany({ take: 50, cursor: cursor ? { id: cursor } : undefined })
}Deterministic comment-block parse: flags blocks that reference a plan or spec (`step 2 of the plan`, `per the spec`, `from the task`) or narrate before/after state (`previously this`, `used to`, `no longer needed`, `replaced the old`).
export async function listInvoices(cursor?: string) {
// Capped at 50 rows because the export worker times out on larger pages.
return db.invoice.findMany({ take: 50, cursor: cursor ? { id: cursor } : undefined })
}Move change history and plan context to the commit message or PR description. Keep source comments for what the code needs explained now.
Agents narrate their plan and their edits into the source. Once merged, the plan is gone and the comment is stale.
ai-slop/meta-comment
ai-slop
Deterministic comment-block parse: flags blocks that reference a plan or spec (`step 2 of the plan`, `per the spec`, `from the task`) or narrate before/after state (`previously this`, `used to`, `no longer needed`, `replaced the old`).
Comments with a why or TODO marker (because, since, otherwise, TODO, FIXME, HACK, note:, workaround), license headers, lint-suppression directives, JSDoc with meaningful tags, Rust doc comments, and non-production paths are not flagged.
Introduced in aislop v0.9.5.