FEATURE REQUEST: Initial setup and integration of GitHub Agent into the core workflow

[smokeyScraper]

Is your feature request related to a problem?

• Yes, it is related to a problem

Describe the feature you'd like

🌟 Feature Description

This feature introduces a new, specialized GitHub Agent into the Devr.AI ecosystem. This agent will act as a "backend" expert, responsible for all interactions with GitHub repositories, including code analysis, issue management, and documentation generation. Its introduction requires updating the core LangGraph workflow to include a new routing path and handoff mechanisms between the existing DevRel Agent and this new agent.

🔍 Problem Statement

Currently, the DevRel Agent is conceptualized as a monolithic entity responsible for all tasks. This creates several problems:

1. Lack of Specialization: The agent's logic becomes overly complex by mixing community engagement tasks with technical, repository-specific tasks.
2. Scalability Issues: As more GitHub-related features are added, the single agent becomes a bottleneck and harder to maintain.
3. Separation of Concerns: There is no clear boundary between conversational logic (handled by DevRel) and automated, non-conversational backend tasks (the role of the GitHub Agent).
   This feature request will solve this by creating a dedicated agent for all GitHub-related operations, leading to a more modular, scalable, and maintainable system.

🎯 Expected Outcome

1. A new GitHubAgent class is created, containing its own ReAct loop and a toolkit with placeholder tools (WebSearch, DocGenerationWorkflow, IssueCreationWorkflow, etc.).
2. The central gather_context_node (the router) is updated to include a conditional edge that routes tasks classified as github to the new GitHub Agent.
3. A clear handoff mechanism is established, allowing the DevRel Agent to pass a task to the GitHub Agent and, crucially, for the GitHub Agent to pass the result back to the DevRel Agent for user-facing communication.
4. The system can successfully execute a full lifecycle request: a user asks the DevRel agent to create an issue, it's handed off to the GitHub agent to perform the creation, and the result is handed back to the DevRel agent to confirm completion with the user.

📷 Screenshots and Design Ideas

Record

• I agree to follow this project's Code of Conduct
• I want to work on implementing this feature