Proposal: Coding Practice Analytics Integration (LeetCode & Competitive Programming)

[imuniqueshiv]

Overview

CommitPulse has evolved beyond a GitHub contribution badge generator and now provides features such as Developer Score, Achievements, Historical Trends, Burnout Radar, PR Insights, CI Analytics, and Repository Analytics.

I would like to propose exploring a new Coding Practice Analytics module that complements existing GitHub-based metrics with coding-practice activity from platforms such as LeetCode.

---

Motivation

Many developers, especially students and early-career engineers, measure their growth through two major areas:

1. Real-world development activity (GitHub)
2. Problem-solving and interview preparation (LeetCode)

While CommitPulse already provides deep insights into GitHub activity, coding-practice data could provide additional context about a developer's learning journey and consistency.

---

Potential Analytics

Examples of metrics that could be explored:

Activity Metrics

• Total problems solved
• Easy / Medium / Hard breakdown
• Daily solving streak
• Longest streak
• Weekly and monthly progress

Contest Analytics

• Contest participation history
• Contest rating
• Rating progression over time
• Personal best rating

Skill Insights

• Topic-wise breakdown
  • Arrays
  • Strings
  • Trees
  • Graphs
  • Dynamic Programming
  • Greedy
  • Binary Search
  • etc.

Achievement System

Examples:

• First Problem Solved
• 100 Problems Solved
• 30-Day Solving Streak
• Contest Milestones
• Difficulty-Based Achievements

---

Why It Could Fit CommitPulse

CommitPulse already focuses on developer growth through:

• Developer Score
• Achievements
• Historical Trends
• Burnout Radar
• Contribution Analytics

A Coding Practice Analytics section could extend this vision and help transform CommitPulse into a more complete developer growth dashboard.

---

Questions for Maintainers

• Does this direction align with the long-term vision of CommitPulse?
• Should CommitPulse remain focused exclusively on GitHub data, or would external developer platforms also fit the roadmap?
• Would maintainers be interested in a more detailed proposal/RFC if the idea aligns with project goals?

I would love to hear feedback from maintainers and contributors before investing time into designing a more detailed specification.

[JhaSourav07]

• Does this direction align with the long-term vision of CommitPulse?

it does, and i really liked the idea.
i am interested in more detailed proposal