Coding Agent with GitHub Integration

Coding Agent with GitHub Integration

Give the agent a plain-English task and it plans the implementation, writes or updates files in your GitHub repository, commits the result, and posts a formatted Slack notification with the file names and commit reference.

What this workflow does

1. TaskInput receives a free-text coding task
2. CodingAgent uses Sequential Thinking to plan before touching any file
3. Agent creates or updates files via the GitHub MCP server
4. Agent commits with a descriptive message and pushes to the repository
5. Agent calls the SlackNotifier tool and posts a formatted mrkdwn summary
6. FinalResult captures the agent's completion text for debugging

Use cases

• Automated utility function generation from a ticket description
• Configuration file updates across repositories
• Test generation for existing functions without manual test writing
• Documentation updates triggered by an API change description

MCP and credential setup

GitHub MCP — Add your GITHUB_PERSONAL_ACCESS_TOKEN to the Agent node's MCP connection env field. The token needs repo scope for private repositories or public_repo for public ones. The MCP server is installed automatically by npx -y.

Sequential Thinking MCP — No credentials needed. Add the connection as shown and reference sequentialThinking in the system prompt to force a planning step before any file write.

Slack — Add a Slack incoming webhook credential to the SlackNotifier node. The node is wired to the agent via the tool-input handle so the agent calls it as a tool and composes the message itself.

System prompt tips

• Instruct the agent to call sequentialThinking before any file operation
• Include Slack mrkdwn formatting rules in the prompt: bold is *text*, links are <URL|text>, double asterisks are not valid
• Set maxToolIterations to at least 20 so the agent has room for planning steps plus GitHub calls
• Set temperature to 0.1 for deterministic code generation