issue-investigation Skill
Investigates GitHub issues in microsoft/aspire by gathering issue context, routing to specialized skills, preparing the right reproduction environment, reproducing behavior, and drafting evidence-backed findings or insufficient-info comments for user approval. Use when asked to investigate, reproduce, validate, debug, Published by microsoft in aspire.
What is issue-investigation Skill?
Investigates GitHub issues in microsoft/aspire by gathering issue context, routing to specialized skills, preparing the right reproduction environment, reproducing behavior, and drafting evidence-backed findings or insufficient-info comments for user approval. Use when asked to investigate, reproduce, validate, debug, Published by microsoft in aspire. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Deployment
- Browser automation use cases
- Deployment use cases
Technical details
- Install or run with Copy skill directory
When to use issue-investigation Skill
- Use it for browser automation.
- Use it for deployment.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/aspire
- Skill file: .agents/skills/issue-investigation/SKILL.md
What it does
Investigates GitHub issues in microsoft/aspire by gathering issue context, routing to specialized skills, preparing the right reproduction environment, reproducing behavior, and drafting evidence-backed findings or insufficient-info comments for user approval. Use when asked to investigate, reproduce, validate, debug,
Skill instructions
Aspire Issue Investigation You are a specialized issue investigator for the microsoft/aspire repository. Your job is to turn an issue into a clear, evidence-backed result: reproduced, not reproduced, needs more information, duplicate/known, or ready for a fix. Do not jump directly to a code change unless the user explicitly asked for a fix and you have enough evidence to know what is wrong. Core rule: context before reproduction Most Aspire issues only reproduce with the right environment: SDK/CLI version, install route, OS, shell, template, AppHost language, package feed/channel, cloud subscription, browser/VS Code setup, external services, or CI artifacts. Gather that context first, then choose the smallest environment that can faithfully reproduce the issue. Prefer the current OS and local machine first; only move to another OS, VM, container, or cloud environment when the issue is explicitly OS/environment-specific, a local attempt cannot reproduce the reported behavior because a r
Explore related resources
Frequently asked questions
What is issue-investigation?
issue-investigation is a open-source AI agent skill with Copy skill directory. Investigates GitHub issues in microsoft/aspire by gathering issue context, routing to specialized skills, preparing the right reproduction environment, reproducing behavior, and drafting.
Who is issue-investigation best for?
issue-investigation is best for reusing agent instructions, scripts, and references, browser automation workflows, deployment workflows.
How do I install issue-investigation?
Install or run issue-investigation using Copy skill directory. Check issue-investigation for the latest setup command.
Is issue-investigation actively maintained?
issue-investigation may need a closer maintenance check before production use.
Auto-fetched from GitHub.
