DataWithBaraa/claude-code-data-engineering-skills / skills/big-review
big-review
UnverifiedUse once a month, or when the platform feels slow, heavy or cluttered, to review the whole platform from the query logs and the repo, and propose improvements with effort and risk.
Big review
The job: one review of the whole platform, from what the consumers use to what nobody uses, every proposal with its effort and risk. It changes nothing.
Input: the period, the last month by default, with at least 90 days of query logs for the unused data.
Steps
- Usage: the most read tables, the slowest queries, and the rows scanned against the rows needed.
- Unused data: the tables and columns nobody read in the last 90 days, checked against the month-end, quarter-end and year-end jobs, the stale tables, and the storage they take.
- Dead code: the functions, parameters and SQL that nothing uses.
- Code health: duplicated logic, outdated documents and the longest functions.
- Data quality: the checks per layer, and the layers without any.
- Proposals: each one with the effort and the risk, in order of priority. A table is deprecated first and dropped only after its owner agrees.
- Give the result as one web page.
Output
One HTML file, like references/big-review.html: the numbers on top, one section per step with a chart or a table, the proposals last. Read it for the layout before you write the page.
Reads
- the query logs, the catalog, the pipeline code, the documents
Writes
- the web page only
Never
- Never changes anything: it proposes, the data engineer decides.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| 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 fallback | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| 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 always | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |