Commit History
-
chore: rename project HireSense -> Hiree
Hemish Jain +1: Claude Opus 4.8Rebrand all display/product name occurrences (README, HF Space title, backend module headers, frontend UI strings) from HireSense to Hiree. Infrastructure identifiers are intentionally left unchanged to avoid breaking the live deployment: the hiresense.db SQLite filename, the hemish22/hiresense HF Space repo id, and the hiresense123.vercel.app / hemish22-hiresense.hf.space URLs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>e597a68
-
feat(pipeline): delete candidate from pipeline tab
Hemish JainAdd DELETE /candidates/{id} route, deleteCandidate API client fn, and a trash button on each kanban card with confirm + optimistic removal (reverts on failure) that also drops the candidate from the compare tray.2bfc96c
-
feat: talent map, applicant portal, pipeline, analytics + deploy readiness
Hemish Jain +1: Claude Opus 4.8Major feature additions: - Team Gap Analysis: per-member model, risk-adjusted coverage, bus-factor, upskill paths, composition radar, what-if editor, compare (removed salary) - 3D Talent Map: semantic PCA constellation of candidates (react-three-fiber) - Applicant portal (/apply): public careers site + status lookup; auto-evaluates and stores every application - Candidate detail route + AI hire verdict (Groq) - Hiring pipeline (Kanban + per-job ranking + compare), recruiting insights (supply vs demand), natural-language candidate search, gap->talent bridge - Jobs model + seeded postings; analytics + matching + ai_summary services Deploy readiness & security: - env-driven CORS (fix wildcard+credentials), upload validation (PDF, size cap, sanitized filenames), removed stale static-serving - Dockerfile + docker-compose + .dockerignore, frontend env template - Detailed README with setup + HF Spaces/Vercel deploy steps, MIT LICENSE - Drop unused spacy dependency Co-Authored-By: Cl…7195215
-
feat(phase-8): complete gemini integration, radar charts, and mass pdf uploader
Hemish Jain262bf96 -
feat(phase-4): API wiring + frontend team results (plan 4.3)
Hemish Jain- POST /api/teams/analyze: full pipeline with Pydantic validation - Frontend: coverage ring, gap clusters, hire plan, salary, expandable JDs - CSS: urgency-colored cards, budget summary, JD expand/copy - DB persistence for team analysesce63b91 -
feat(phase-3): scoring engine + frontend results display (wave 2)
Hemish Jain- ScoringEngine: orchestrates skill match, learning, credibility scoring - Dynamic weight redistribution when GitHub/LeetCode unavailable - Recommendation engine: Strong Hire/Hire/Maybe/Pass thresholds - Frontend: score ring, 5 score cards, skill tags, predictions, flags - API returns full ML scoring with explanations - DB stores computed match/learning/credibility/overall scores358b6c7
-
feat(phase-2): leetcode analyzer + full pipeline wiring (wave 2)
Hemish Jain- LeetCodeAnalyzer: GraphQL API, problem-solving + difficulty balance scores - Full pipeline: upload PDF → parse → GitHub → LeetCode → combined result - POST /api/candidates/analyze accepts file + JD + optional usernames - Database record saved with all analysis data - Verified end-to-end with real GitHub/LeetCode users6e01c05 -
feat(phase-1): project structure, FastAPI skeleton, SQLite models
Hemish Jain- FastAPI app with CORS, lifespan DB init, router registration - Pydantic Settings config (DATABASE_URL, GITHUB_TOKEN) - Health, candidates, teams route handlers - CandidateAnalysis and TeamAnalysis SQLAlchemy models - History and detail endpoints for both models - requirements.txt with all dependencies - README.md, .gitignore, .env.example795d690