Feature Description
As it stands, the Github Weekly Org report skill iterates over all the repos of the organization. This is unnecessarily wasteful because of the recent rossoctl renaming effort, and it ends up polluting the context of the repo with details on repositories that are no longer "core".
Proposed Solution
We should restrict the skill (especially the deterministic scripts) to focus on a curated set of "core repos" as recently defined in the automation repo. This enables us to tune the repos under consideration in a single point.
Of course, in the spirit of the automation refactoring design spec, this is also intended to simplify the porting of these skills to other orgs.
Want to contribute?
Additional Context
The current version of the skill: https://github.com/rossoctl/agent-skills/blob/main/skills/github-weekly-report/SKILL.md
Feature Description
As it stands, the Github Weekly Org report skill iterates over all the repos of the organization. This is unnecessarily wasteful because of the recent rossoctl renaming effort, and it ends up polluting the context of the repo with details on repositories that are no longer "core".
Proposed Solution
We should restrict the skill (especially the deterministic scripts) to focus on a curated set of "core repos" as recently defined in the automation repo. This enables us to tune the repos under consideration in a single point.
Of course, in the spirit of the automation refactoring design spec, this is also intended to simplify the porting of these skills to other orgs.
Want to contribute?
Additional Context
The current version of the skill: https://github.com/rossoctl/agent-skills/blob/main/skills/github-weekly-report/SKILL.md