What is michelangelo-component-splitter?

This is a command line tool that automatically breaks up oversized React Native screens into smaller, separate component files. It targets the common problem of a single screen file growing to hundreds or thousands of lines, by finding logical chunks of the code and pulling them out into their own well-formed files. What sets this version apart is that it understands the actual project it is working on. If it finds a tsconfig.json file, meaning the project uses TypeScript, it loads the real type information the same way a code editor would, so the props it generates for each new extracted component have accurate types instead of generic guesses. If a prop's type depends on custom types defined elsewhere, the tool copies or imports those definitions so the new file still works correctly, falling back to a generic type only when it cannot safely resolve something. After splitting a file, the tool runs a real TypeScript type check on exactly the files it touched. If that check finds an error, it automatically undoes the whole operation, restoring the original file and removing the newly created ones, rather than leaving broken code behind. It also saves a backup copy of the original file before making changes. Inline styles used inside the component are pulled out into a shared styles file, with identical style objects reused instead of duplicated. If an extracted piece is still too large, the tool can run itself again on that new file, up to a configurable depth. The README is candid about its limits: shared style matching only catches exact duplicates, recursive splits could in rare cases create duplicate imports, generated test stubs are only basic smoke tests, and it has been tested against a small representative project rather than large-scale real-world Michelangelo-generated code. No license is mentioned in the README, so its reuse terms are not stated.