Repository Access and Contributor Permissions Audit
Review who has admin, write and read access on your GitHub organisation or repo, spot leavers and over-broad roles, and plan a safe cleanup.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
This is a defensive audit of access to our own GitHub organisation or repository [ORG_OR_REPO]. I will paste a list of members, teams, outside collaborators and their roles (read, triage, write, maintain, admin), plus any deploy keys, apps or tokens listed: [ACCESS_LIST]. I will also tell you who has left or changed role recently: [ROLE_CHANGES]. The repositories that matter most are [CRITICAL_REPOS]. Return: 1) A table with the columns Person or app, Role, Where, Concern (leaver, contractor with admin, unused app, personal access, no team, duplicate access) and Recommended action. 2) Counts of admins, outside collaborators, and bots or apps, and the admin share of total members with the arithmetic. 3) The people with access to critical repos beyond what their team role suggests. 4) A least-privilege model: which teams, which roles, and who should be the two or three admins. 5) A cleanup plan with steps in a safe order: confirm with managers, reduce rights before removing, rotate credentials where relevant, record the change. Use only the list pasted; do not assume a person has left unless I said so. Do not remove access automatically; every change needs an owner approval. Role names and available settings depend on the GitHub plan, so mark specifics [VERIFY]. This is a review of our own environment and not a formal security assessment.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.