feat: add Node.js Agentic Issue Resolver to agents

[Impesud]

Hi team! I'm submitting a new agentic sample.

This project provides a resilient implementation of a developer agent using the GitHub Copilot SDK, specifically optimized to handle the current Technical Preview limitations regarding file modifications.

Compliance:

Follows the AGENTS.md guidelines.

Includes frontmatter and proper file naming (.agent.md).

Moved to a standalone repo as recommended by @friggeri in the copilot-sdk repo.

Looking forward to your feedback!

[aaronpowell]

I'm not really sure that this makes sense as an agent, since it's a standalone sample. We are looking at the best way to support external samples in this repo, so I'll keep the PR open as we refine that

[Impesud]

I'm not really sure that this makes sense as an agent, since it's a standalone sample. We are looking at the best way to support external samples in this repo, so I'll keep the PR open as we refine that

Thanks for the feedback, @aaronpowell ! I understand the distinction. I created this as a standalone repository to provide a complete, end-to-end example of a resilient agentic workflow.

I'm happy to wait while you refine the structure for external samples. If you decide to create a 'Community Samples' or 'External Projects' section, I'd be glad to see this included there. Let me know if you need me to move the metadata file or adjust the description in the meantime!

[aaronpowell]

#632 is open to bring the cookbook across from the SDK repo, but I think we'll want a better way to list out external samples.

@Impesud what's your thought on some kind of YAML file that external samples, such as yours, could be listed in and then we'll have a script that automates surfacing them in the repo? Or do you have other thoughts on how to surface them in the repo?

[Impesud]

#632 is open to bring the cookbook across from the SDK repo, but I think we'll want a better way to list out external samples.

@Impesud what's your thought on some kind of YAML file that external samples, such as yours, could be listed in and then we'll have a script that automates surfacing them in the repo? Or do you have other thoughts on how to surface them in the repo?

Hi @aaronpowell , I think the YAML approach is the most scalable path forward. It turns this repository into a structured registry, making it easier for scripts to generate tables, galleries, or even a searchable site in the future.

Here is a proposal for a schema that could live in a external-samples.yaml file:

# Proposed schema for external-samples.yaml
samples:
  - id: nodejs-agentic-issue-resolver
    name: "Node.js Agentic Issue Resolver"
    description: "A resilient agentic workflow for autonomous codebase exploration and fixing, optimized to handle Technical Preview limitations."
    url: "https://github.com/Impesud/nodejs-copilot-issue-resolver"
    author:
      name: "Impesud"
      url: "https://github.com/Impesud"
    sdk_version: "Technical Preview" # Useful for tracking breaking changes
    tags: [nodejs, copilot-sdk, agents, automation]
    resilience_features: true # Optional: highlighting samples that solve specific SDK hurdles

I am more than happy to be the first to adopt this format. If you decide to go this way, let me know if you'd like me to create the initial YAML file or if you have a specific location in mind for it.

[aaronpowell]

We could probably leverage https://github.com/github/awesome-copilot/blob/main/cookbook/cookbook.yml

Let me have an experiment around with some structure

[Impesud]

We could probably leverage https://github.com/github/awesome-copilot/blob/main/cookbook/cookbook.yml

Let me have an experiment around with some structure

That makes perfect sense, @aaronpowell . Leveraging cookbook.yml is a great way to maintain consistency across the repo. I'm ready to adapt my contribution once you’ve defined the new structure. Standing by for your updates!