Skip to content

Adding a skill for AppDomain migration - #13

Closed
marklio wants to merge 4 commits into
dotnet:mainfrom
marklio:marklio/appdomain_migration
Closed

Adding a skill for AppDomain migration#13
marklio wants to merge 4 commits into
dotnet:mainfrom
marklio:marklio/appdomain_migration

Conversation

@marklio

@marklio marklio commented Feb 12, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@marklio

marklio commented Feb 12, 2026

Copy link
Copy Markdown
Contributor Author

@dotnet-policy-service agree company="Microsoft"

@marklio
marklio marked this pull request as ready for review February 12, 2026 20:30
@jeffschwMSFT
jeffschwMSFT requested a review from agocke February 12, 2026 21:01

@jeffschwMSFT jeffschwMSFT left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please rebase this skill into the new repro structure and run through the skill validator

@ManishJayaswal

Copy link
Copy Markdown
Contributor

@marklio - please update this to the new repo structure and run evals ( see contributing.md file for guidelines).

@marklio marklio closed this by deleting the head repository Mar 10, 2026
YuliiaKovalova added a commit to YuliiaKovalova/skills that referenced this pull request May 7, 2026
Changes to make the model follow the R->P->I pipeline without
prompt-level forcing:

1. Remove escape hatch: deleted 'skip the pipeline' row from
   examples and simplified 'Why no Direct' callout
2. Gate language: model CANNOT write tests until .testagent/
   research.md and plan.md exist
3. Few-shot example: concrete <example> showing correct first
   action (runSubagent researcher, NOT writing tests directly)
4. Required first action: explicit STOP sign before Step 3
   saying first action MUST be code-testing-researcher
5. Prohibitive rule dotnet#13: MUST NOT use edit/create to write
   test files — only code-testing-implementer creates them

Benchmarking context: agent instructions land in <agent_instructions>
XML tags in the user message. The model treats XML-wrapped content
as advisory, not binding. These changes use imperative language,
gate conditions, and few-shot examples to overcome that gap.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
moesac0970 pushed a commit to moesac0970/skills that referenced this pull request Jul 4, 2026
…lers pattern, Swashbuckle/Asp.Versioning, no controllers/minimal APIs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants