lucas-lima-s

repo-audit

Audits any repository against publish-ready standards before it goes public: secret and API-key scan, author-identity and internal-term scan across the whole git history, test execution, language-vs-declared-stack, README image rot, staleness and GitHub description/topics quality. Also runs over a list of repos and renders a portfolio dashboard. Use when the user says 'audit this repo', 'is this ready to publish', 'check for secrets before I push', 'audit my whole portfolio', '/repo-audit', or in pt-BR 'audita esse repo', 'esse repo ta pronto pra publicar?', 'varre meus repos antes de publicar'.

base-skill

Reference skill that ships with claude-skill-audit as a functional example. Triggered by "run base-skill" / "rode a base-skill". Prints `ok` and exits.

polylint

Run the project's own lint stack over a file or directory in three phases - replay the repo's pre-commit hooks, run read-only analyzers in parallel, then propose fixes for approval - and report an honest per-tool status instead of a silent pass. Use whenever code has just been written or edited and needs validation, or when the user asks to lint, check style, or validate a file. Triggers on "lint this", "run lint", "check code style", "validate this file", "rode lint", "valide os lints", "/polylint".

Data & Documents Listed

todo

Manage the user's PERSISTENT cross-session TODO list (data/TODO.md, bidirectionally synced with the Notion page "TODO"). Use when the user triggers /todo, asks to add/list/complete/remove items from their personal list ("adiciona na minha lista", "anota pra depois", "o que tá pendente?", "marca X como feito"), or mentions a future idea worth saving ("uma hora preciso fazer X" → offer to add it). NOT for tracking steps of the current session's task — only for items that must survive the conversation.

timesheet

Generate a weekly work summary from git history across all your repositories, with hour estimates derived from commit timestamps. Use when the user asks for a timesheet, hours worked, a weekly summary, or triggers /timesheet.

Data & Documents Listed

pyright-envs

Generate a pyrightconfig.json with one executionEnvironment per package so that Go to Definition in a monorepo resolves each file against its own import paths instead of another package's vendored copy of the same module. Use when Ctrl+click jumps into the wrong package, after a hard clean removed pyrightconfig.json, on a fresh clone, or when the set of packages changed. Triggers on "go to definition is going to the wrong package", "regenerate pyrightconfig", "pylance resolves the wrong copy", "regenerar pyrightconfig", "o ctrl+click foi pro pacote errado".

Web & Frontend Listed

react-legacy-review

Review React 16 plus Redux-Saga code in a legacy browser-rendered app against a checklist organized by failure mode - render identity, effect dependencies, saga concurrency, store shape, bundle size, DOM cost - and flag advice that silently assumes React 18 or a server framework. Use when reviewing or editing React components, containers, sagas, selectors or reducers in an older codebase. Triggers on "review this React component", "React 16 review", "redux saga review", "legacy frontend review", "revisa esse componente React", "checklist React legado".

layered-review

Review the current local diff in layers - a generic code-review pass plus the domain reviewer subagents whose paths the diff touches - then consolidate everything into one deduplicated, severity-grouped report. Never commits; reports only. Use before opening a pull request or when the user asks for a thorough local review. Triggers on "layered review", "review my local diff", "run the review agents", "revisao local", "revisa meu diff local", "/layered-review".

API & Backend Listed

notebooklm-router

Decide where a question should be answered - a NotebookLM notebook holding authoritative documents, this project's source code, its local docs, its issue tracker, or a third-party reference - and apply the citation policy for whichever source is chosen. Use before answering any question that a loaded document corpus might cover, or when the user asks about a specification, standard, statute or manual. Triggers on "check the spec", "what does the standard say", "query the notebook", "consulta a especificacao", "o que diz a norma", "pergunta pro notebook".