Gino Canessa
Community@GinoCanessa
@Microsoft working on healthcare standards and interoperability, focused on FHIR.
Agent Skills by Gino Canessa
Showing 9 vetted skills indexed across 1 GitHub repositories.
dev-pr-open
Pushes committed branches and opens draft pull requests with changelog entries and issue references.
dev-issue
Publishes slot feature requests and bug reports as GitHub issues via gh CLI.
dev-approach
Generates three isolated solution designs and a judged selection from a feature request or bug report.
dev-report
Drafts and iterates structured bugreport.md files for local development defects.
dev-do
Executes implementation plans phase by phase with verified local commits.
dev-plan
Generates phased implementation plans from feature requests or bug reports.
dev-review
Runs dual engineering and QA review passes over a change scope and synthesizes findings into analysis.md.
dev-complete
Orchestrates the full local development loop from raw request to local commits.
dev-request
Drafts and iterates structured feature request documents as a staff-level Product Manager.
Frequently Asked Questions About Gino Canessa
FAQPage SchemaWhat tasks can I accomplish with Gino Canessa's dev skills?▼
The nine skills cover the full local development loop: drafting feature requests and bug reports, contesting three solution approaches with a judging pass, building phased implementation plans, executing code changes with local commits, running dual engineering/QA reviews, publishing GitHub issues, and opening pull requests.
Who are these dev skills designed for?▼
They target software engineers and engineering leads who want role-based assistance across the development lifecycle. Each skill adopts a staff-level persona—Product Manager, Tech Lead, Engineering Lead, QA Lead, or release engineer—to produce structured artifacts like plan.md, analysis.md, and bugreport.md.
How do the skills run in practice?▼
Each skill accepts a full file path or a short slot number expanding to scratch/[MMDD]-[##]/, auto-discovering source artifacts there. Optional max_subagents caps parallel fan-out, checkpoint_every yields control after N phases, and dev-complete chains the entire pipeline from raw request to local commits.
Do these skills push code or write to GitHub automatically?▼
No. GitHub integration is strictly opt-in: dev-issue and dev-pr-open act only when the repository's AGENTS.md contains a '## GitHub Integration' section with 'Enabled: yes'. All other skills commit locally only and never push, open pull requests, or publish artifacts.
What are the prerequisites for using these skills?▼
A repository using the scratch/[MMDD]-[##]/ slot directory convention for artifacts such as featurerequest.md, bugreport.md, plan.md, and analysis.md. GitHub publishing additionally requires the AGENTS.md opt-in section; everything else operates purely on local files and commits.