Merge branch 'main' into dependabot/npm_and_yarn/serialize-javascript-7.0.5

Author: janechu

.github/copilot-instructions.md

@@ -41,6 +41,9 @@ These contain domain-specific guidance. Read when performing related tasks:
 
 - [TypeScript](./skills/typescript/SKILL.md) — compiler constraints, import/export conventions, decorator usage, testing patterns.
 - [Shipping](./skills/shipping/SKILL.md) — pull request format, change file generation, documentation updates.
+- [Pull Request](./skills/fast-pull-request/SKILL.md) — generate a pull request description from the branch diff.
+- [Bug Report](./skills/fast-bug-report/SKILL.md) — generate a bug report issue from conversation context.
+- [Feature Request](./skills/fast-feature-request/SKILL.md) — generate a feature request issue from conversation context.
 
 ## Commands
 

.github/skills/fast-bug-report/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: fast-bug-report
+description: Generate a bug report issue for the FAST repository using the provided template.
+---
+This prompt only applies to generating Bug Report issues for the FAST repository.
+
+Do not create or modify any existing Github issues. This skill is only for
+generating the markdown content for a new issue based on the provided template.
+
+Based on the conversation context, generate a bug report as a markdown code
+block using the template located at
+[../../ISSUE_TEMPLATE/bug-report.md](../../ISSUE_TEMPLATE/bug-report.md).
+
+The summary should clearly state what the bug is and which part of the system
+is affected.
+
+Repro or Code Sample should provide clear, minimal steps to reproduce the issue.
+Include a code snippet, repository link, or gist if possible.
+
+Expected Behavior should describe what the correct behavior should be.
+
+Current Behavior should explain what actually happens instead. Include the full
+error message and stack trace if applicable. Mention screenshots if they would
+help illustrate the problem.
+
+Possible Solution is optional. Include it only if there is a concrete idea about
+the cause or fix. Mention if the reporter is willing to contribute a fix.
+
+Context should explain how the bug affects the user and what they are trying to
+accomplish. This helps prioritize and design the right solution.
+
+Your Environment should capture relevant details: OS, device, browser, and
+package version.
+
+Search for existing open or closed issues that overlap with this bug report.
+If duplicates or related issues exist, mention them in the Context section.
+
+Suggest a concise issue title in the format `fix: [what is the issue?] in [where is the issue?]`.
+
+Provide the markdown code block only, without any additional commentary or explanation.
+
+Any comments in the template can be removed since they're only meant to provide
+guidance on how to fill out the template, and are not intended to be part of the
+final issue body.

.github/skills/fast-feature-request/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: fast-feature-request
+description: Generate a feature request issue for the FAST repository using the provided template.
+---
+This prompt only applies to generating Feature Request issues for the FAST repository.
+
+Do not create or modify any existing Github issues. This skill is only for
+generating the markdown content for a new issue based on the provided template.
+
+Based on the conversation context, generate a feature request as a markdown code
+block using the template located at
+[../../ISSUE_TEMPLATE/feature-request.md](../../ISSUE_TEMPLATE/feature-request.md).
+
+The summary should clearly state what the feature is and why it matters, focusing
+on user value rather than implementation details.
+
+Expected Behavior should describe how the feature would work from an end-user or
+developer perspective. Be specific about the desired outcome.
+
+Current Behavior should explain the gap — what exists today and how the absence of
+this feature affects users. If there is a workaround, mention it briefly.
+
+Possible Solution is optional. Include it only if there is a concrete implementation
+idea worth capturing. Prefer high-level direction over prescriptive code.
+
+Context should explain the motivation — what the user is trying to accomplish
+and why this feature would help. Mention alternatives that were considered, if any.
+
+Examples is optional. Include it when code snippets, screenshots, or usage
+scenarios would clarify the request.
+
+Search for existing open or closed issues that overlap with this feature request.
+If duplicates or related issues exist, mention them in the Context section.
+
+Suggest a concise issue title in the format `feat: add [what] to/in [where]`.
+
+Provide the markdown code block only, without any additional commentary or explanation.
+
+Any comments in the template can be removed since they're only meant to provide
+guidance on how to fill out the template, and are not intended to be part of the
+final issue body.

.github/skills/fast-pull-request/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: fast-pull-request
+description: Generate a pull request description for the FAST repository using the provided template.
+---
+This skill only applies to generating Pull Request descriptions for the FAST repository.
+
+Do not create or modify any existing Github pull requests. This skill is only for
+generating the markdown content for a pull request description based on the provided template.
+
+Based on the conversation context, generate a pull request description as a markdown code
+block using the template located at
+[../../pull_request_template.md](../../pull_request_template.md).
+
+Use the Pull Request Template to generate a markdown code block for the most
+relevant work on this git branch, compared to `main`.
+
+The Description should be either a summary description of the content of the branch,
+or a list of the most relevant changes made in the branch. The goal is to address
+the purpose of the pull request in a concise manner, rather than detailing every change. "Why"
+and "what" over "how".
+
+Determine if any current github issues are being addressed by this work, and
+list them in the Issues section with links. If none are found, remove the Issues section.
+
+The reviewer notes section is optional. Include it only if there are specific
+areas where you would like feedback or attention from the reviewer.
+
+The Test Plan section should outline any issues that need to be verified before merging,
+or steps to reproduce the behavior locally. Even a brief note is helpful, such as "All existing tests pass".
+
+The checklist section should be completed to indicate the status of various
+aspects of the pull request.
+
+If there are change files that have been added to the PR, check the box labeled "I have included a change request file using `$ npm run change`".
+
+If any new tests have been added, check the box labeled "I have added tests for my changes."
+
+Check the terminal output for evidence of passing tests, and check the box labeled "I have tested my changes." if tests have been run and are passing. If not, leave the box unchecked.
+
+If any doc blocks have been added or modified, or if any documentation files have been added or modified, check the box labeled "I have updated the project documentation to reflect my changes." This also applies to any changes made to api-report files.
+
+The final checkbox must be checked by the pull request author. It should never be checked when generating this PR description.
+
+The Next Steps section is optional. Include it only if there are specific follow-up tasks
+or work items that should be addressed after merging this PR, such as updating documentation, adding new tests, or performing code cleanup. If any existing issues are being addressed by the next steps, reference them here.
+
+Provide the markdown code block only, without any additional commentary or explanation.
+
+Any comments in the template can be removed since they're only meant to provide
+guidance on how to fill out the template, and are not intended to be part of the
+final PR description.