Skip to content

fix: keep Prettier and Biome away from skills-lock.json - #180

Merged
chenjiahan merged 3 commits into
rstackjs:mainfrom
upupming:fix/ignore-skills-in-formatters
Sep 11, 2026
Merged

fix: keep Prettier and Biome away from skills-lock.json#180
chenjiahan merged 3 commits into
rstackjs:mainfrom
upupming:fix/ignore-skills-in-formatters

Conversation

@upupming

@upupming upupming commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

skills-lock.json is written by the skills CLI, but the Prettier and Biome templates did not ignore it, so formatting a new project could rewrite it. Ignore it in both. Skill directories under .agents are left to each project, since they may also hold skills the project maintains.

Skills are installed into .agents with their hash recorded in
skills-lock.json, but neither was ignored, so formatting a new project
rewrote third-party skill files. Ignore both in the Prettier and Biome
templates.

@chenjiahan chenjiahan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ignoring all of .agents seems too broad: it can also contain project-maintained skills that should follow the project's formatting rules. The template cannot reliably distinguish those from installed third-party skills.

Could we keep the skills-lock.json exclusion and leave skill directory exclusions to individual projects for now?

.agents can also hold skills a project maintains itself, which should
follow its formatting rules, so leave excluding skill directories to
each project.
@upupming upupming changed the title fix: keep Prettier and Biome away from installed skills fix: keep Prettier and Biome away from skills-lock.json Sep 11, 2026
@upupming

Copy link
Copy Markdown
Contributor Author

Makes sense. Now only skills-lock.json is ignored, and .agents is left to each project.

Comment thread test/skills-ignore.test.ts Outdated

@chenjiahan chenjiahan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@chenjiahan
chenjiahan marked this pull request as ready for review September 11, 2026 05:21
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 11, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-11T05:24:05.829177Z 08f2b59 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chenjiahan
chenjiahan merged commit a79d88b into rstackjs:main Sep 11, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants