repository-setup

This skill provides a critical configuration workflow for contributors to the libuipc project who are working with forked repositories. By default, the GitHub CLI (gh) and other git utilities may associate issues and pull requests with a user's personal fork rather than the upstream repository. This tool ensures that all development activities, including bug reporting, feature tracking, and pull request management, are correctly routed to the spiriMirror/libuipc repository.

Designed for developers, contributors, and researchers engaged in GPU-based incremental potential contact (IPC) simulations, this configuration is essential for maintaining project integrity and workflow automation. It streamlines interaction with the central codebase, ensuring that Cursor AI agents and CLI commands correctly reference the canonical source of truth for all simulation-related data and metadata.

• Ensures correct remote repository association by adding the upstream repository pointer.

• Standardizes the use of the --repo spiriMirror/libuipc flag for accurate issue and PR synchronization.

• Simplifies collaborative development for those maintaining both local forks and upstream clones.

• Compatible with standard git and GitHub CLI (gh) environments, requiring no extra infrastructure.

• Users must execute the provided git remote add command within their local repository environment.

• It is recommended to verify the connection using git remote -v to confirm the upstream pointer is correctly registered.

• Ideal for users managing C++20 and Python-based simulation codebases where precise version control and contribution tracking are paramount.

• Note that this skill is specific to the libuipc workflow and should be initialized immediately upon cloning a personal fork to avoid command redirection errors.