Inspiration Inspired by Formula 1, where a Race Engineer ensures every mechanical change aligns with the team's strategy, MergeMechanic brings that same precision to software development. We wanted to solve the problem of "Logic Drift"—where developers inadvertently skip critical security or architectural requirements defined in Jira during the coding phase.
What it does MergeMechanic bridges the gap between Jira and Bitbucket. When a developer pushes code, the app automatically:
Fetches linked Jira ticket requirements (like MER-1 for Security Auth).
Uses AI to compare the code diff in the Pull Request against those specific requirements.
Acts as a "Gatekeeper" by flagging the PR as FAILED if the logic (like "auth" keywords) is missing, ensuring only "Race Ready" code is merged.
Challenges I ran into Integrating real-time Bitbucket web triggers with the Forge environment required precise manifest configuration. Mapping natural language requirements from Jira to technical code changes in Bitbucket using AI was a complex but rewarding hurdle to overcome.
Technologies Used Atlassian Forge, Bitbucket API, Jira API, JavaScript/JSX.
Log in or sign up for Devpost to join the conversation.