github-projectslisted

# GitHub Projects Skill ## Overview Every repository in the `QuantumSensing` organisation has exactly one associated GitHub Project. The project name matches the repository name. The Kanban board has five columns driven by the `Status` single-select field: ``` Backlog → Todo → In Progress → In Review → Done ``` Issues are the unit of work. PRs are linked to issues. Claude moves issues through the board automatically as work progresses. The human approves the task breakdown before coding starts. --- ## Fork mode A forked repository within `QuantumSensing` is treated as an independent project. It has its own issues, its own project board, and its own labels. PRs target the fork's own `main` — not the upstream. There is no assumption of eventual upstream contribution. ### Detecting fork mode At session start (or project init), check whether the repo is a fork: ```bash curl -s \ -H "Authorization: Bearer $GITHUB_TOKEN" \ -H "Accept: application/vnd.github+json" \ "https://api.github.com/repos/QuantumSensing/{repo}" \ | python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('fork', False), d.get('parent', {}).get('full_name', ''))" ``` If the first token is `True`, this is a fork. Store: ``` IS_FORK = true UPSTREAM_REPO = <parent full_name> # e.g. QuantumSensing/original-repo ``` ### Fork mode differences | Behaviour | Greenfield | Fork | |---|---|---| | Issues | Created on this repo | Created on this repo | | Project board | Created on this repo