jj-clone-third-party

To clone a third-party repository for isolated inspection, this Skill uses a deterministic jj git clone workflow to fetch external repos into a dedicated work/ directory, ensuring the exploration remains separate from your main project history.

Exploring upstream dependencies without polluting git history is achieved by cloning repositories into a gitignored work/ directory, providing a non-destructive workspace that isolates third-party source code from your main repository.

Yes, you can use jj to clone external repositories into a specific work/ directory. The Skill applies a deterministic jj git clone workflow to fetch repositories into work/<descriptive-name> for independent examination and research.

Cloning third-party repos in isolation directly helps with debugging upstream issues by allowing you to safely fetch and inspect external source code locally in a dedicated work/ directory without affecting your main project.

You should isolate third-party repository clones to prevent external code from polluting your main repository history. This non-destructive approach allows safe exploration of API usage patterns and upstream implementations in a gitignored workspace.

The limitation of using a dedicated work/ directory for third-party research is that the cloned repositories are isolated for examination only, meaning changes made in this gitignored workspace will not be integrated back into your main project history.