AI Blocks › Keep your code secure
Code ownership analyst
Point it at a git repo. Get who owns the sensitive code and where one person is the only owner.
Code ownership analyst is a free AI skill for the job "Keep your code secure". Give the instructions to an AI assistant that supports the required files and tools, then review its output.
Free · No account · Apache 2.0 licence · Made by OpenAI · Level: advanced
Made by OpenAI. See the original on GitHub; we copied it as it is, with its licence.
What it does
A map of who really owns your sensitive code, and where a single person is the only one who knows it. It turns git history into risk you can act on. A Python script reads the commit history and links people to files. It marks sensitive areas using default rules or your own list, and flags files with one owner or owners who have left. It also builds a co-change graph, grouping files that tend to change together while ignoring huge noisy commits and glue files like lockfiles. You can query the results as small slices and export them to Neo4j or Gephi. It needs Python 3 and networkx.
You give it
- A git repository
- A time window (optional)
- A list of sensitive paths (optional)
- Python 3 with networkx
You get
- People-to-file ownership map
- Single-owner risk flags
- Clusters of files that change together
- Export files for graph tools
Use it when
- One engineer left and you do not know what they alone understood.
- You want to see who owns your auth and payment code.
- You need to find files that always change together.
- An audit asks who is responsible for sensitive areas.
How to use it
- Add it to your AI once: download it and add the folder to Claude, ChatGPT or Codex as a skill.
- Ask for the job in your own words. Your AI opens the skill when it fits.
- It works best when your AI can run code and read your git history.