Stats
Actions
Tags
From project-lens
Update all stale .lens feature docs after a work session. Run this after code review or after a batch of commits to keep docs current. Part of the standard workflow: code review → commit → update.
How this skill is triggered — by the user, by Claude, or both
Slash command
/project-lens:updateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Rescan all files changed since the last lens update.
Rescan all files changed since the last lens update.
# Get files changed in last N commits or since .lens was last modified
git diff --name-only HEAD~5 HEAD 2>/dev/null | \
grep -E '\.(ts|tsx|js|jsx|py|go|rs|php|rb|java|vue|svelte)$'
.lens/index.md to find which feature docs need updatingbash ${CLAUDE_PLUGIN_ROOT}/scripts/scan.sh <file> <project_root>
After every significant task, the workflow is:
/review or manual)/lens:update — keep docs currentThis ensures the next session starts with accurate context.
npx claudepluginhub 0serenvale/project-lens --plugin project-lensResearches current code state and updates corresponding documentation to keep docs in sync with code.
Checks whether project documentation is up-to-date after code changes by scanning git diffs and reporting stale or missing docs.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.