Claude Code
Your HackIndia proof is a public GitHub repo. It should show three things: Claude Code-ready context, safe shared settings, and reviewed code changes through commits or a pull request.
Do not add a big feature now. Package the work you already built.
0 of 7 lessons done · proved by a submitted project with a public repository
Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.
0 of 6 done
git status
git diff
git log --oneline -5When Claude Code runs in your repo, it can access files in that directory and subdirectories. It can also see git state, including your current branch, uncommitted changes, and recent commit history.
That is useful, but it means your final repo should be clean before you submit. Keep .env, API keys, local database dumps, debug logs, and .claude/settings.local.json out of git.
Use CLAUDE.md as the operating guide for future Claude Code sessions. Keep it real. Do not list fake commands just to look complete.
For example, a college fest UPI expense splitter could use this:
# Claude Code project context
Project: UPI Expense Splitter for college fest teams.
Stack:
- Client: React in client/
- Server: Node and Express in server/
- Data: local JSON storage for hackathon demo
Commands:
- Install root dependencies: npm install
- Start dev server: npm run dev
- Run client build: npm run build
- Run tests if present: npm test
Conventions:
- Keep UI text simple for Indian college users.
- Amounts are stored in rupees as numbers.
- Do not add paid services or external APIs unless asked.
- Do not read or modify .env files.
- For multi-file changes, propose a plan first.
Review checklist:
- Run npm run build before final commit.
- Check git diff before committing.
- Mention any untested area in the commit or PR notes.Shared project settings belong in .claude/settings.json. Personal overrides belong in .claude/settings.local.json and should stay out of git.
For a public hackathon repo, deny reads of environment files. Claude Code permission rules are deny-first, so a deny rule cannot be allowed back by another settings level.
mkdir -p .claude
cat > .claude/settings.json <<'EOF'
{
"permissions": {
"deny": [
"Read(./.env)",
"Read(./.env.*)"
]
}
}
EOF
cat > .gitignore <<'EOF'
.env
.env.*
node_modules/
dist/
build/
.claude/settings.local.json
EOF
git statusDo each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.
0 of 5 done
git diff -- CLAUDE.md .claude/settings.json .gitignore
npm run build
# In Claude Code, run local review:
/code-review
# Then commit:
git add CLAUDE.md .claude/settings.json .gitignore server/routes/expenses.js client/src/pages/GroupSummary.jsx
git commit -m "Add reviewed CSV export for expense summaries"
git status
git remote -v
git push origin mainDo not submit a private repo. Open the GitHub link in an incognito window or ask a teammate to check it before you paste it into HackIndia.
Do not assume Claude Code reads AGENTS.md directly. It reads CLAUDE.md. If you already have AGENTS.md, import it from CLAUDE.md.
# Optional if you already have AGENTS.md
cat > CLAUDE.md <<'EOF'
@AGENTS.md
Additional Claude Code rules:
- Do not read .env or .env.* files.
- Propose a plan before multi-file changes.
- Run the listed build or test command before final commits.
EOFIf you use a GitHub pull request, Claude Code Code Review can post findings as inline comments. A top-level @claude review comment can trigger review where it is configured.
These findings do not approve or block the PR. You still own the final review.
Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.
0 of 5 done
Answer the quick check to finish this lesson.