Skip to content

DataWithBaraa/claude-code-data-engineering-skills / skills/knowledge-refresh

knowledge-refresh

Unverified

Use after a release, to compare the knowledge Claude Code reads, CLAUDE.md, the standards, the source pages and the incident log, with the code and the data, and propose what is stale, missing or wrong.

Knowledge refresh

The job: keep the knowledge that Claude Code reads true to the project: CLAUDE.md and the knowledge folder. It proposes, and after the data engineer's yes it writes the approved changes. The runbook and the how-to guides belong to the docs skill.

Input: none, or the area to check.

Steps

  1. CLAUDE.md: every folder it names exists, every skill is listed, every path is right.
  2. The standards against the code: naming, layers, code style.
  3. The sources against the contracts and the files: one page per source, current.
  4. The business: the glossary and the stakeholders against the documents.
  5. The architecture and the core model against what is built.
  6. The known issues and the incident log: what a run has proven since. The incident skill adds the entries, this skill checks them.
  7. The decision log: what is decided, what is still open.
  8. A document nobody has read yet: what it adds to the knowledge.
  9. Keep it short: what repeats another file is cut and linked.
  10. Report every finding as a proposal: the file, what it says, what is true.

Output

A list of proposals, one per finding: the file, what it says, what is true, and the change. After the yes, the approved changes in the knowledge files.

Reads

  • the knowledge, the code, the data contracts, the documents, the run records

Writes

  • nothing until the yes, then only the knowledge files the data engineer approved

Never

  • Never applies a change without the yes.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 318kUpdated Claude CodeCodexUnverifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 318kUpdated Claude CodeCodexUnverifiedInstall