Loading...
Loading...
Fix code in a named change or file list so it matches the conventions its own repository already keeps: run the project's configured formatter and linter in fix mode through the project's own toolchain, then fix by hand what no tool decides (naming, import order, file layout, error style) toward the dominant pattern in neighbouring files, behavior preserved, and ask with counts where the repository keeps two competing conventions. Use for 'make this match the codebase', formatter or linter setup, naming consistency, or a style pass on a change under review. Acts only inside the change or files the user names.
npx skill4agent add lilmgenius/paperthin re0-stylere0-stylenode scripts/scope.mjs <files...> [--json]linguist-generatedlinguist-vendorednpm execbun run./node_modules/.bin/uv runpoetry run--versiongit show <base>:<path>dedashdedotdebloat