write-issue-cowork

Format and post GitHub issues and pull requests for Cedanl repositories.

Updated Nov 8, 2024
One-click install
npx skills add https://github.com/cedanl/.github --skill write-issue-cowork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-issue-cowork
Source: https://github.com/cedanl/.github/tree/main/.claude/skills/write-issue-cowork
Command: npx skills add https://github.com/cedanl/.github --skill write-issue-cowork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wrapper around the GitHub MCP connector that ensures Cedanl issue templates are applied so issues and PRs have the correct format when created or updated from Cowork.

Core Features & Use Cases

  • Generate properly formatted issue bodies from Cedanl ISSUE_TEMPLATE files.
  • Determine issue type and apply appropriate templates (Bug, Pitch, Task) in Cowork.
  • Submit and report the resulting html_url via the issue_write tool.

Quick Start

Create a new issue in Cowork, select the correct type, fill the required sections per the template, and submit to format via the issue_write tool.

Frequently Asked Questions about write-issue-cowork

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue formatting using templates in Cowork?

Automating GitHub issue formatting in Cowork applies repository-specific issue templates like Bug, Pitch, or Task during creation or editing. The process validates issue types via the GitHub MCP connector and applies the correct template structure before submitting the final formatted issue.

What GitHub MCP connector is needed to post issues from Cowork?

Posting issues from Cowork requires a connected GitHub MCP connector configured for the target repositories. The connector enables the issue_write tool, which validates repository issue types and returns the html_url of the created or updated issue as a response.

How do I ensure my GitHub pull requests follow Cedanl repository issue templates?

Ensuring GitHub pull requests follow Cedanl templates involves applying standardized formatting through an automated wrapper around the GitHub MCP connector. This enforces correct body structure based on predefined ISSUE_TEMPLATE files during the pull request creation or update workflow.

Can I edit existing GitHub issue metadata to match repository templates in Cowork?

Editing existing GitHub issue metadata to match repository templates in Cowork is supported during active sessions. The tool determines valid issue types using list_issue_types(owner="cedanl") and reformats titles or bodies to align with the required template structure.

Why do my GitHub issues lose their template format when created from Cowork?

GitHub issues lose their template format when created from Cowork if the GitHub MCP connector is not properly connected or the issue type validation is bypassed. Applying the dedicated formatting wrapper ensures the repository ISSUE_TEMPLATE structure is enforced before submission.

What issue types are supported when formatting GitHub issues for Cedanl repositories?

Supported issue types for Cedanl repositories include Bug, Pitch, and Task categories. The tool queries valid types using list_issue_types(owner="cedanl") through the GitHub MCP connector and applies the corresponding ISSUE_TEMPLATE format to the issue body.