You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Maintenance: stop asking contributors to regenerate the agent skill references #8806
Since #8745 the agent skill references in .agents/skills/.../references/ are generated from docs/ and a test in CI fails when the committed files are out of date. The idea was to never let them drift. In practice it moved the cost to the wrong people.
What happened this week:
The release workflow bumps the layer version in the docs (chore(ci): layer docs update) through a bot PR that does not run pre-commit. After 3.40.0 every reference with a layer ARN was one version behind, and every PR that updated its branch from develop started failing test_agent_skill_references for a change it did not make (fix(logger): empty or unparsable POWERTOOLS_DEV no longer crashes Logger #8783).
Four of the ten PRs in the 3.41.0 milestone touch docs and all four fail the same test, because the author did not run pre-commit or regenerated against an older develop. None of them knew the file existed.
That is a barrier for people fixing a sentence in the docs, and the fix is on our side.
What I want to change:
Remove the test from the PR workflow. A docs PR changes docs, nothing else.
Add a workflow on push to develop, filtered to docs/** and examples/**, that runs scripts/build_agent_skill_references.py and commits the result if anything changed. References catch up minutes after a merge, including the release bot's PR.
Keep the pre-commit hook for those who have it installed; it just stops being required.
Make the generator drop the layer ARN tables and the version number from the references. For an agent, one line pointing to the installation page is more useful than thirty ARNs that change every release, and it removes 300 lines of churn per release.
Until this lands I will push the regeneration commit on the affected PRs myself so nobody has to deal with it.
This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Activity
powertools-for-aws-oss-automation commentedon Nov 14, 2026
Warning
This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
github-actions commentedon Nov 18, 2026
This is now released under 3.41.0 version!