The Open Source Bridge: An AI-Powered Engine for Your Next Major Contribution

Jash Patel — Sun, 01 Mar 2026 23:26:55 +0000

This is a submission for the DEV Weekend Challenge: Community

The Community

I built this for the aspiring developer community — specifically the students, recent graduates, and early-career engineers who are often overwhelmed by the sheer scale of the open-source world. As a recent Master of Science in Computer Science graduate from the University of Kansas and a Data Analyst, I have seen firsthand how difficult it is to find that first meaningful contribution that actually helps build a professional portfolio. This project serves the community of developers who want to transition from academic learning to shipping real-world code by bridging the gap between raw data and actionable contribution opportunities.

What I Built

The Open Source Bridge is an AI-driven discovery engine designed to eliminate "contribution paralysis". While many platforms list "good first issues," they often lack context or include stale data. My app uses a custom-built Bridge Score algorithm to rank issues based on their quality and availability.

Key features include:

Dynamic Ranking: A Pandas-powered scoring system that identifies the "Sweet Spot" for new contributors.
AI Summarization: Integration with the Groq LPU (Llama 3.3 70B) to provide instant, 1-sentence TL;DR summaries and technical "first steps".
Portfolio Pipeline: A professional, glassmorphism dashboard that turns open-source discovery into a streamlined career-building experience.

Demo

Code

dev-jash15 / open-source-bridge

A Personalized Matchmaker for Aspiring Contributors.

🌉 The Open Source Bridge

"Bridging the Gap Between Code and Career."

💡 Main Motivation

Early-career developers, including Master of Science in Computer Science graduates and professional Data Analysts, often face "contribution paralysis". While they possess the technical skills, finding a welcoming, relevant, and "active" project in the vast sea of GitHub is a complex data problem.

The Open Source Bridge was built to solve this. It is a discovery engine that uses Data Science to rank opportunities and Groq AI to provide an instant roadmap for the first pull request. It is designed specifically for developers looking to transform academic knowledge into industry-ready portfolio contributions.

🏗️ System Architecture

The project utilizes a decoupled "Power Stack" to ensure speed, data integrity, and a premium user experience.

Frontend: Next.js 14, React, and Tailwind CSS for a high-performance "glassmorphism" dashboard.
Backend: FastAPI (Python) providing an asynchronous bridge between data…

View on GitHub

How I Built It

Building this required a full-stack approach that balanced high-speed data processing with an aesthetic, user-centric interface.

Backend (FastAPI & Python): I leveraged FastAPI for its asynchronous capabilities and Pandas to handle the real-time data transformation required for the ranking algorithm.
Data Intelligence (The Bridge Score): I developed a weighted formula to calculate issue priority:

BridgeScore = (Recency * 0.5) + (Relevance * 0.3) + (Friction * 0.2)

AI Layer (Groq): To provide instant insights, I integrated the Groq API to analyze issue descriptions and generate professional outreach drafts for users.
Frontend (Next.js & Tailwind CSS): I utilized Next.js 14 and TypeScript to build a language-agnostic dashboard that supports any programming ecosystem a developer might be learning, from Python to Rust.

Next Steps

Scalable Caching: Transitioning from local JSON storage to a distributed Redis layer for production-grade performance.
Direct Engagement: Integrating GitHub OAuth to allow users to post their AI-generated outreach drafts directly from the dashboard.
Personalized ML: Developing a recommendation model that suggests issues based on a developer's specific repository history and skill set.

Final Thoughts

Building this tool was a journey in combining my background in data analysis and software engineering to solve a problem that impacts us all. As someone who recently completed my Master of Science in Computer Science, I know the pressure of trying to stand out in a competitive field. The Open Source Bridge is my contribution to a community that thrives on collaboration and growth. My goal is to help every developer move past the "where do I start?" phase and get straight to the impactful work that defines a career. I’m excited to see how this tool helps you land your next big role or merge your first major PR. Let’s keep building!

Cupid-Commit 💘 - Finding the Code That Completes You

Jash Patel — Sat, 14 Feb 2026 07:49:36 +0000

This is a submission for the GitHub Copilot CLI Challenge

What I Built

Cupid-Commit is a custom GitHub Copilot CLI extension that acts as a "Couples Counselor for Code."

With Valentine's Day upon us, I wanted to build something fun but technically complex. I recently built a project called Codebase Cartographer to visually map out codebase dependencies, which got me thinking about how different repositories "communicate." What if we could use AI to figure out if two different tech stacks would make a good match?

I built a Node.js CLI tool that accepts any two remote GitHub repositories as arguments. It uses the GitHub CLI (gh repo view) to dynamically scrape their languages, descriptions, and popularity. It then feeds this "DNA" into a custom GitHub Copilot Agent (.agent.md) using programmatic mode.

The AI categorizes the repositories into archetypes (like The Romantic, The Stoic, or The Socialite), analyzes their tech-stack compatibility, and outputs a perfectly formatted Markdown file containing a Compatibility Report and a Love Letter from Repo A to Repo B.

Demo

GitHub Repository: https://github.com/dev-jash15/cupid-commit

My Experience with GitHub Copilot CLI

Working with the Copilot CLI ecosystem was an incredible learning experience, especially when pushing the boundaries of non-interactive automation.

1. Taming the Custom Agent (.agent.md): I learned that you can enforce incredibly strict personas using the .agent.md framework. By defining "Core Directives" and "Tone Constraints," I was able to force the LLM to completely abandon standard coding assistance and strictly act as a witty relationship counselor, outputting beautifully formatted markdown instead of raw JSON or code snippets.

2. Bypassing the Programmatic Sandbox: The biggest technical hurdle I faced was the CLI's security sandbox. I wanted to use programmatic mode (copilot -p) to fully automate the pipeline. However, in this mode, Copilot strictly restricts access to files outside the current working directory.
To solve this, I engineered a "Drop and Clean" strategy using Node.js. My orchestrator script:

Fetches the remote repository data using gh commands.
Writes that data to a hidden .temp-dna.json file directly inside the user's current directory.
Copies my .cupid.agent.md file into the same directory.
Executes the Copilot CLI using the @file operator to read those local temp files.
Captures the output, strips the CLI telemetry, and automatically deletes the temporary files to leave the user's workspace perfectly clean.

This combination of standard Node orchestration and Copilot's @file context mapping allowed me to build a highly dynamic, multi-repo tool that feels completely native to the terminal.

Forem: Jash Patel

The Open Source Bridge: An AI-Powered Engine for Your Next Major Contribution

The Community

What I Built

Demo

Code

dev-jash15 / open-source-bridge

A Personalized Matchmaker for Aspiring Contributors.

🌉 The Open Source Bridge

💡 Main Motivation

🏗️ System Architecture

How I Built It

Next Steps

Final Thoughts

Cupid-Commit 💘 - Finding the Code That Completes You

What I Built

Demo

My Experience with GitHub Copilot CLI