supportmail-to-ticket

Automating support email triage to GitHub issues requires connecting Gmail MCP, GitHub CLI, and Filesystem MCP. The skill retrieves emails, searches the local codebase for context, and drafts structured issues with an approval workflow before creation.

Yes, linking Gmail messages to existing GitHub issue threads is supported. The skill processes incoming support emails and files generated issues against existing threads in the repository to maintain continuous context and tracking.

Yes, a local codebase is required to draft GitHub issues from support emails. The skill uses Filesystem MCP to search local codebase files, extracting relevant code references to provide context and suggested next steps for the issue draft.

The approval workflow for creating GitHub issues from emails requires user confirmation before issue creation. The skill generates an anonymized issue draft with code references and suggested next steps, pausing for user review to ensure accuracy.

Automated email triage handles code references by searching the local codebase via Filesystem MCP during a dedicated processing phase. It extracts relevant code context to include in the anonymized GitHub issue draft, ensuring technical accuracy before the approval step.

Limitations of using Gmail MCP for GitHub issue automation include strict dependencies on GitHub CLI and Filesystem MCP for codebase search and issue creation. The skill is specifically tailored for the erp-mafia/gnubok repository and requires local filesystem access to function properly.