Hey Finance Engineers,
Every finance team needs a GitHub now.
When all our finance engineers started building, we didn’t only see the token usage boom :) We saw a mess. Everyone’s files somewhere else. Nothing standardized. Automations that went on vacation with their owners.
A shared GitHub repo fixes it. Every skill in one place, with history - something breaks during close, you open last month’s version. Nothing goes live without review. Company data stays out of the logic, so one skill works for every entity.
As a CFO or finance leader using AI, setting this up is your job. Not IT’s.
This one’s for my Pro subscribers: the exact setup, the folder structure, what goes in every file, the review process, and our template. It took us weeks to figure out. You’ll have it running in an afternoon.
Let’s go.
Step 0 - Why GitHub and not a shared Drive folder
A folder holds files, not history. When a skill breaks during close, you can’t roll back to last month’s version. And anyone can overwrite anything.
GitHub is a drive for your skills and code, plus three things a folder can’t do:
History. Every version of every file, forever.
Review before merge. A change waits until a teammate approves it.
Separation. Reusable logic and company data live in different places, with different permissions.
Seven words you’ll meet along the way:
Repo - a project folder GitHub tracks.
Branch - your personal draft.
Commit - saving a change with a note about why.
Pull Request (PR) - “I changed something, please review it.”
Merge - the approved change joins the shared version.
Step 1 - Accounts and the organization
Who: the CFO or whoever owns finance ops. This takes 15 minutes.
1/ Go to github.com and create a free account if you don’t have one.
2/ Create an organization (top-right menu → New organization → Free plan). Name it after your company: acme-finance. An organization is a shared home for repos, so they belong to the team, not to one person’s account.
3/ Ask every person on the finance team to create a GitHub account and send you their username.
4/ Invite them to the organization: Organization → People → Invite member.
That’s the whole team on GitHub.
Nobody needs to know anything else yet.
Step 2 - Create two repos, not one
This is the rule that makes everything safe. Two repos:
finance-agents- skills, agents, workflows, and rules. No company data inside. Every person on the team has access.