canvas-issue

Create GitHub issues from agent-canvas sessions with element context and screenshots.

3|1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/edrouhardmicrosoft/agent-canvas-skills --skill canvas-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canvas-issue
Source: https://github.com/edrouhardmicrosoft/agent-canvas-skills/tree/main/.claude/skills/canvas-issue
Command: npx skills add https://github.com/edrouhardmicrosoft/agent-canvas-skills --skill canvas-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill streamlines creating GitHub issues directly from agent-canvas sessions, automatically capturing selected UI elements, page context, and screenshots to support bug reports and feature requests.

Core Features & Use Cases

  • Automated issue generation: Create a GitHub issue with a curated body including page URL, session data, and selected elements.
  • Rich context for developers: Attach element selectors, screenshots, and design rules to speed feedback.
  • Use Case: While QA testing a design, trigger issue creation from a problematic screen to report the bug with precise context.

Quick Start

From the agent canvas UI, click Create Issue after selecting elements, fill in title/description, and let the skill generate and submit the issue to your configured GitHub repo.

Frequently Asked Questions about canvas-issue

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

FAQPage Schema
How do I create GitHub issues from agent canvas sessions?

To create GitHub issues from agent canvas sessions, select problematic UI elements, click Create Issue, enter a title and description, and the skill submits the issue to your configured repo with page context. It relies on the gh CLI for authenticated creation.

What context does automated issue generation capture for design QA bug reports?

Automated issue generation for design QA captures selected UI elements, page URLs, screenshots, and session data. This rich context provides developers with precise selectors and design rules to speed feedback during bug hunts.

Do I need the gh CLI to automate issue creation from UI screenshots?

You do not strictly need the gh CLI to automate issue creation from UI screenshots. The skill relies on the gh CLI when authenticated for creating issues, but can fall back to generating a web URL if authentication is unavailable.

Can I upload UI screenshots to GitHub as part of an automated bug report?

Yes, you can upload UI screenshots to GitHub as part of an automated bug report. The skill builds the issue body from session data and optionally uploads captured screenshots to a gist for attachment.

What is the best way to report UI bugs with element selectors and page information?

The best way to report UI bugs with element selectors and page information is using a skill that curates issue bodies from canvas sessions. It packages selections, screenshots, URLs, and session data into actionable reports for developers.

Does canvas issue creation work without an authenticated GitHub repository?

Canvas issue creation can work without an authenticated GitHub repository by falling back to a web URL for submission. However, authenticated gh CLI access is required for fully automated issue generation directly to the repo.