* Add visual-pr plugin: screenshot capture, annotation, PR embedding, and screen recording
Four skills that teach Copilot to capture UI screenshots (Playwright + PIL),
annotate them with algorithmic label placement, embed before/after images
in PR descriptions, and record animated GIF demos.
Includes demo images showing the annotation engine on GitHub Issues.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Update generated README tables and marketplace.json
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Embed annotate.py module in image-annotations skill
The full working module (annotate_image, grid_image, diff_images) is now
included as a code block so users can save it as annotate.py and import
directly. Scrubbed project-specific labels from examples.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Address review feedback: mss.mss() context manager, fix RECT struct, consistent placeholder
- Use mss.mss() context manager instead of mss.MSS() (ui-screenshots, screen-recording)
- Fix broken RECT struct in window+GIF combining example (screen-recording)
- Consistent projectId placeholder in AzDO upload example (pr-screenshots)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* fresh pull of updated stage with 2 skills and updated README only
* adjusted skills after feedback and used skill analyser to review
---------
Co-authored-by: Mark Heynes <mutl3y@heynes.biz>
Adds a skill that lets users generate images (icons, sprites, textures,
mockups) directly from their coding workflow using OpenAI gpt-image-2 or
Google Gemini. BYO API key — the skill guides users through setup on
first use.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Replace manual curl/PowerShell download instructions with the
Copilot CLI slash command: /skills add johnpapa/ai-ready
This is simpler, cross-platform, and matches the upstream repo's
install instructions.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The REST API for issue field values is simpler and avoids common
pitfalls with the GraphQL approach (needing special headers, node IDs,
option IDs vs names). Key changes:
- Add REST API section as the recommended approach
- Document correct payload format (issue_field_values array wrapper)
- Document that value takes the option NAME not ID for single-select
- List common mistakes (wrong key format, missing wrapper, -f vs --input)
- Move GraphQL to an alternative section (still documented)
- Remove outdated private preview notice (now in public preview)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>