I fixed my first real bug in open source at GSSoC 2026
I've been participating in GSSoC 2026 (GirlScript Summer of Code) and today I got my first real code bug fix merged. Not a README edit. Not adding to a list. An actual bug fix in Python code.
Here's exactly what happened.
The Bug
In the project prajwalsuryawanshi/agentapi, there was a function called to_tool_definition().
The problem — when a developer used the @tool decorator to give their tool a custom name, description and context, the function was completely ignoring all of that. It was just using the raw function name and raw docstring instead.
So if you wrote:
@tool(name="my_custom_tool", description="does something useful")
def some_function():
"""raw docstring"""
pass
The tool definition would show some_function and raw docstring — completely ignoring what the developer wrote in the decorator. That's a real bug.
What I Fixed
Just 3 lines changed. But those 3 lines fixed the entire problem.
-
to_tool_definition()now reads the custom tool name from the@tooldecorator - It now uses the composed description and context instead of the raw docstring
Clean, minimal, focused fix.
The Labels on My PR
The maintainer added these labels before merging:
gssoc:approvedlevel:beginnertype:bugtool calling
Even a CodeRabbit AI bot reviewed it and said "No actionable comments" which basically means the code was clean enough that even the bot had nothing to complain about 😄
What I Learned
Before this I thought open source contributions had to be huge. Like adding entire features or rewriting systems.
This was 3 lines. But it fixed a real problem that real developers using this library were hitting.
That's what open source actually is — finding something broken and making it slightly less broken.
My GSSoC journey so far
This is my first week properly contributing to open source.
Before this I also got a PR merged in pcqpcq/open-source-android-apps (10k+ stars) where I added 3 missing apps to a curated list.
But this bug fix feels different. This was actual code. This was finding a real problem, understanding why it was broken, and fixing it properly.
More contributions coming. If you're also doing GSSoC 2026 feel free to connect — always happy to help beginners get their first PR merged!
Top comments (0)