Skip to content

notque/vexjoy-agent / skills/code-quality/comment-quality

comment-quality

Verified

Review and fix temporal references in code comments.

references/temporal-keywords.txt

View on GitHub
# Temporal Keywords Reference
# Complete list of words that indicate temporal references in comments
# Use this list for automated scanning and validation

## Primary Temporal Words
new
old
previous
current
now
recently
latest
modern
legacy
original

## Development Activity Words
added
removed
deleted
updated
changed
modified
fixed
improved
enhanced
refactored
optimized
revised
altered
adjusted
amended
corrected
patched
tweaked
upgraded

## State Transition Words
replaced
migrated
upgraded
deprecated
became
turned into
evolved
transformed
converted
switched
moved from
changed from

## Temporal Phrases (Multi-word)
as of
since
from
after
before
used to
will be
going to
in the future
at some point
eventually
soon
later
earlier

## Version References
in v2
post-1.0
pre-refactor
after release
before version
since version
as of release

## Comparison Words (Relative)
better than
worse than
faster than
slower than
more efficient than
less efficient than
instead of
rather than
unlike
compared to
in contrast to

## Development Process Words
implementing
implementation of
addition of
removal of
fix for
workaround for
temporary
interim
placeholder
stopgap

## Problem/Solution Language
this fixes
this solves
addresses issue
resolves bug
handles problem
deals with
works around
prevents issue
avoids problem

## Improvement Language
improvement
enhancement
optimization
better
superior
advanced
streamlined
simplified
cleaner

## Historical References
originally
initially
previously
formerly
at first
in the beginning
used to be
was
were

## Future References
TODO: remove when
FIXME: change after
will need
should eventually
planned for
scheduled for
upcoming
future

## Time-Based References
today
yesterday
tomorrow
last week
next month
this year
currently
presently
at present
at the moment

## Allowed Exceptions
# These words CAN be used in specific contexts:

@deprecated        # Part of deprecation annotation
Generated by       # Code generation marker
Copyright          # Legal notice
Since:             # Javadoc/API version tag (when required by framework)
Version:           # API version documentation (when describing API contract)
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall