Add agent skill for required input dependency migrations#20100
Merged
teresaromero merged 4 commits intoJul 15, 2026
Conversation
Guides agents through discover-decide-execute-verify with decision gates for dataset naming, variable overrides, and tests before editing packages. Co-authored-by: Cursor <cursoragent@cursor.com>
mrodm
reviewed
Jul 13, 2026
|
|
||
| ## Phase 1 — Discover the package | ||
|
|
||
| 0. Confirm `elastic-package version` succeeds. If missing, stop and point to the [elastic-package install guide](https://github.com/elastic/elastic-package#getting-started). |
Collaborator
There was a problem hiding this comment.
Should it be added the minimum elastic-package version for this ? Is v0.125.1 ?
|
|
||
| | Decision | Options / prompt | | ||
| | --- | --- | | ||
| | Field mapping fixes | Any `long` → `double` or similar fixes? (`bugfix` changelog) | |
Collaborator
There was a problem hiding this comment.
It could be added here that it is needed to check for any breaking changes if there are updates in the mapping types.
Comment on lines
+167
to
+169
| elastic-package test policy -v | ||
| elastic-package test system | ||
| elastic-package test |
Collaborator
There was a problem hiding this comment.
Why not running just elastic-package test ?
Is it to show all the possible errors in policy and system tests independently ?
Contributor
Author
There was a problem hiding this comment.
i usually first run policy tests; have them green; then move to system and finally run the whole suite. But an agent can run just test and get the feedback from all. 👍🏻
| - [ ] Pipeline regression tests for edge cases found during migration | ||
| - [ ] Changelog entries: migration, stack constraint, field-mapping fixes | ||
| - [ ] Docs manually updated if `{{ inputDocs }}` is empty | ||
| - [ ] Dashboards validated on the target stack version |
Collaborator
There was a problem hiding this comment.
Same as in elastic/elastic-package#3753 (comment)
Contributor
Author
There was a problem hiding this comment.
I've aligned this with the how-to guide (last commit)
andrewkroh
added
the
documentation
…ckage and remove redundant test commands.
…ding implications for existing indices and changelog categorization. Clarify checklist item for changelog entries to specify usage of `breaking-change` for incompatible type updates.
…ification and template binding for migration plans. Clarify the importance of understanding variable layers in agent policy merges and emphasize the need for explicit confirmation on hardcoded values. Update the variable matrix to include intent and template binding details for better clarity during the migration process.
mrodm
approved these changes
Jul 14, 2026
Contributor
|
Queued — the merge queue status continues in this comment ↓. |
Contributor
Merge Queue Status
Waiting for
All conditions
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enhancement
Proposed commit message
Add agent skill for required input dependency migrations.
WHAT:
Adds
.agents/skills/migrate-required-input-dependency/SKILL.md, an agent skill that walks developers through migrating integration packages to use required input dependencies (requires.input,streams[].package). The skill follows a discover → decide → execute → verify workflow with decision gates for dataset naming, variable overrides, stack constraints, and tests before any package files are edited.WHY:
Follow-up to the
elastic_package_registryinput-package migration (#19719). Gives agents and developers a repeatable, gated workflow aligned with the elastic-package how-to guide.Checklist
changelog.ymlfile. (N/A — agent skill only)Author's Checklist
main(blocks merge — TBD)How to test this PR locally
Install the skill from this branch:
Then invoke the skill when migrating an integration (for example, ask the agent to migrate a package to
requires.input) and confirm it runs through the decision gates before editing files.Related issues
Screenshots
N/A
Made with Cursor