Feat/kiro steering file#1388
Open
BALLOON005 wants to merge 4 commits into
Open
Conversation
github-actions
Bot
added
new contributor
Contributor
|
You have 3 docs commits; do a interactive rebase and squash into 2 atomic commits |
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
2 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.
Purpose / Description
When pulling an agent config for Kiro, also generate a Steering file at .kiro/steering/.md with proper YAML frontmatter. Kiro's native instruction system uses Steering files rather than AGENTS.md, so this ensures agents work with Kiro's inclusion modes.
Fixes
Approach
Added Steering file generation to KiroAdapter.format_config() in observal-server/services/ide/kiro.py. The generated file includes YAML frontmatter with inclusion: always, name, and description fields, followed by the agent's rules content. Scope-aware paths are handled — project scope writes to .kiro/steering/, user scope writes to ~/.kiro/steering/. The CLI-side steering_file handler in cmd_pull.py was already in place so no changes were needed there.
How Has This Been Tested?
Code review against the existing agent_file generation pattern in the same adapter and the steering_file handler already present in cmd_pull.py.