Add GitHub devs tools

[marc-aurele-besner]

Add GitHub devs tools

• List currently connected user repositories
• List specific user repositories
• List specific organization repositories
• List forked repositories
• Create a fork from the repository
• Get the default GitHub repository branch
• Create a new branch from another branch
• Create commit GitHub tool
• Create pull request GitHub tool

[jfrank-summit]

What are we waiting on to for this PR? Looks awesome!

[marc-aurele-besner]

What are we waiting on to for this PR? Looks awesome!

Testing I guess, I haven't really tested these tools yet 😓

But I guess

[Xm0onh]

Awesome!
Just a small suggestion:

[jfrank-summit]

It would be worth wrapping these in a GitHub agent, the tool list is getting quite long!

[jfrank-summit]

I think this is great! As discussed earlier, there are a lot of tools here and many of them won't be used by some agents. It would be great if we could group this tools into common use cases (they kind of are now) or scopes and all the creator of a GitHub agent to select the necessary groups for their agent.

[chadlegrand]

Thank you for adding these GitHub developer tools! I've reviewed the changes and have some suggestions to enhance the implementation:

1. Error Handling Pattern
   I agree with @Xm0onh and @jfrank-summit about returning errors instead of throwing them. The suggested pattern with {success, error} object is more agent-friendly and consistent with best practices in async operations. This would make error handling more predictable across the codebase.

2. Model Configuration
   Regarding the Claude model selection, switching to Claude-3-5 as default is a good suggestion. Consider implementing this as a configurable option:

const defaultModelConfig: LLMConfiguration = {
  provider: 'anthropic',
  model: process.env.CLAUDE_MODEL || 'claude-3-5-sonnet-latest'
}

3. Tool Organization
   The activity tools should be included in createGitHubTools() as mentioned. Consider grouping related tools into categories for better organization:

return {
  repos: { list, create, delete, ... },
  activity: { watch, unwatch, ... },
  issues: { create, comment, ... }
}

4. Type Safety

• Consider adding more specific TypeScript types for the GitHub API responses
• Use zod schemas for runtime validation of API responses
• Add type guards where necessary

5. Testing
   Since testing is pending:

• Add unit tests for the new tools using mock responses
• Include integration tests with GitHub's API sandbox environment
• Add test coverage for error scenarios

These changes would improve code maintainability, type safety, and reliability while following Web3 development best practices.