GitHub as Your Knowledge Base.
Objective
Shift how the team thinks about GitHub. It's not just for developers — it's the best place to store everything your AI needs to know. We also got our first look at the CLI and saw a real dashboard QA demo.
Watch the Session
Dhwani RIS members only
Key Concepts
The Problem We Solved
You create a skill file. You want to share it with a teammate. You download it, put it on a cloud drive, they download it, upload it to their Claude UI. Next week you update the skill. Repeat the entire process. Every. Single. Time.
You put your skill in a GitHub repo. Your teammate gets access. Their Claude reads directly from your repo. When you update the skill, everyone gets the update automatically. One update, everyone benefits.
Why GitHub Beats Folders
Version history. Every change is tracked. You can always go back. No more "final_v2_REAL_final.docx".
Live updates. Update once, everyone sees it. No download-upload cycle.
API access. Claude can read from GitHub directly via tokens. It cannot read from your Google Drive.
Collaboration. Multiple people contribute without overwriting each other's work.
Developers already use it. By storing knowledge on GitHub, you speak the same language as the dev team.
Personal vs Org Repos
Personal repo: Your own GitHub account. Private to you. For your CLAUDE.md, personal skills, preferences. No PR required — you commit directly.
Org repo: Dhwani RIS shared repository. Security MD, domain skills, coding standards. Changes require a PR and developer approval.
CLI Introduction
We got our first look at Claude Code — the command-line interface. Key advantages over the chat UI:
No time limits. CLI continues indefinitely. No session timeouts.
Context preservation. If it stops, it picks up where it left off.
Parallel agents. Give it 3 tasks, it sends 3 agents simultaneously.
MCP connections. Connect to Gmail, Slack, Calendar, Apple Reminders — directly from the terminal.
Side questions. Ask something without disrupting the main task using /btw.
CLI is not a replacement for the UI. Use UI for thinking, brainstorming, documents, images. Use CLI for coding, parallel tasks, integrations. Use both.
Real-World Demo: Dashboard QA via Video
Sunchay demonstrated a powerful technique for testing dashboards without writing test code:
Record a 2-minute screen recording of the dashboard — apply filters, scroll through data.
Compress to under 20 MB (Claude's file size limit).
Feed to Claude with a skill that says: read every 2 frames per second, extract all data points, compare against three sources:
The logic sheet (what the values should be)
The API response (what the system returns)
The UI screenshots (what the user sees)
Result: Claude identified matches, flagged mismatches, and even warned about KPIs that were technically correct but might not represent what the user intended. Three-layer validation from a 2-minute video.
Dhwani Repo Structure
For mGrant, there are multiple apps (repos) that work together:
ThemeShared utilities across all products (e.g., draft mode logic)DonorDonor-facing features — grant management for corporate donorsCSRCSR compliance — MCA Section 135 specificClient AppClient-specific customisations — portal, iframes, custom logicKey Takeaways
GitHub is a knowledge repository, not just a code repository. Use it for skills, CLAUDE.md, domain knowledge.
Personal repos are your starting point. No PRs, no approval needed.
CLI and UI serve different purposes. Neither replaces the other.
Video-based QA is real. Test dashboards by recording, compressing, and feeding to AI.
Further Reading
GitHub's official beginner tutorial. 10 minutes to your first repo.
How to edit files directly in the browser — no terminal needed.