Skills lint-fixer
📦

lint-fixer

Content revision r1 Safe ⚙️ External commands

Fix Lint Errors Safely

Lint failures slow reviews and hide real defects. This skill runs lint checks, guides safe fixes, and verifies behavior with tests.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "lint-fixer" from https://skillstore.io/skills/yamadashy-lint-fixer.md and its manifest at https://skillstore.io/api/skills/yamadashy-lint-fixer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/yamadashy-lint-fixer.md Signed manifest GET /api/skills/yamadashy-lint-fixer/manifest Signed lockfile GET /api/skills/yamadashy-lint-fixer/lockfile

Test it

Using "lint-fixer". A TypeScript project fails lint after formatting changes.

Expected outcome:

The assistant runs the lint workflow, applies safe formatting fixes, reruns lint, and reports that tests pass.

Using "lint-fixer". A pull request has both style errors and type errors.

Expected outcome:

The assistant separates automatic style fixes from manual type fixes, updates the code, and explains the remaining decisions.

Using "lint-fixer". A repository reports a possible secret during linting.

Expected outcome:

The assistant stops normal lint repair, highlights the secret warning, and recommends rotating or removing the exposed value.

Security Audit

Safe
v8 • 7/8/2026 Open versioned report

The skill is a straightforward lint repair workflow with no prompt injection, network access, credential access, or data exfiltration intent found. Several static findings are valid because the skill directs an agent to run npm and linter commands, including auto-fix and test scripts that can execute project-defined code. The remaining findings are inline configuration file names and are false positives.

1
Files scanned
39
Lines analyzed
7
Review items
0
False positives ignored
Capability review items (7)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium
SKILL.md:12
Ruby/shell backtick execution
`npm run lint` runs 4 tools in sequence:
The skill describes running npm run lint, which executes project-defined npm script logic. This is expected for lint repair, but it can run arbitrary code from the target repository.
Medium
SKILL.md:14
Ruby/shell backtick execution
1. **Biome** (`biome check --write`) - Formatter + linter, auto-fixes
The Biome command is a hardcoded formatter and linter command with write behavior. It is legitimate, but it executes a workspace tool and can modify repository files.
Medium
SKILL.md:15
Ruby/shell backtick execution
2. **oxlint** (`oxlint --fix`) - Fast JS/TS linter, auto-fixes
The oxlint command is a hardcoded linter command with automatic fixes. It is legitimate, but it executes a workspace tool and can modify repository files.
Medium
SKILL.md:16
Ruby/shell backtick execution
3. **tsgo** (`tsgo --noEmit`) - TypeScript type checking
The tsgo command is a hardcoded TypeScript check with no emit. It still executes a workspace tool, so it remains an external command risk in untrusted projects.
Medium
SKILL.md:21
Ruby/shell backtick execution
1. Run `npm run lint` to identify issues
The workflow instructs the agent to run npm run lint to identify issues. NPM scripts can execute project-controlled code, so this is a real but expected risk.
Medium
SKILL.md:24
Ruby/shell backtick execution
4. Run `npm run lint` again to verify
The workflow instructs the agent to rerun npm run lint for verification. Repeated npm script execution has the same project-controlled command risk.
Medium
SKILL.md:25
Ruby/shell backtick execution
5. Run `npm run test` to ensure no breakage
The workflow instructs the agent to run npm run test. Test scripts are project-defined and may execute arbitrary code, even when used for normal validation.

Risk Factors

⚙️ External commands (10)
SKILL.md:12 SKILL.md:14 SKILL.md:15 SKILL.md:16 SKILL.md:21 SKILL.md:24 SKILL.md:25 SKILL.md:29 SKILL.md:30 SKILL.md:31
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/yamadashy-lint-fixer/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/yamadashy-lint-fixer/security.svg)](https://skillstore.io/skills/yamadashy-lint-fixer?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/yamadashy-lint-fixer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/yamadashy-lint-fixer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/yamadashy-lint-fixer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

yamadashy. (2026). lint-fixer security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/yamadashy-lint-fixer/audits/8

BibTeX citation

@techreport{yamadashy-yamadashy-lint-fixer-2026, author = {yamadashy}, title = {lint-fixer security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/yamadashy-lint-fixer/audits/8}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "lint-fixer security audit report (audit version 8)" version: "unspecified" type: report authors: - name: "yamadashy" date-released: "2026-07-08" url: "https://skillstore.io/skills/yamadashy-lint-fixer/audits/8" identifiers: - type: other value: "skillstore:yamadashy-lint-fixer:audit:8" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
70
Community
91
Spec Compliance

What You Can Build

Clean Up Pull Requests

Fix formatting, lint, and type-check failures before a pull request is ready for review.

Maintain Code Standards

Apply documented project lint rules consistently across TypeScript and JavaScript files.

Validate Generated Changes

Run lint and test checks after code generation to catch style, type, and secret issues.

Try These Prompts

Fix Current Lint Errors 
Run the lint-fixer workflow on this repository. Fix lint errors, preserve behavior, and tell me what changed.
Review Lint Categories 
Run the lint checks, group failures by tool, and fix only the issues that are safe to change automatically.
Resolve Type And Style Issues 
Use the lint-fixer workflow to resolve style issues first, then address TypeScript errors without changing behavior.
Verify A Release Branch 
Run lint and tests, inspect npm scripts before execution, fix failures, and summarize any remaining risk or manual follow-up.

Best Practices

  • Inspect package scripts before running lint or test commands in unfamiliar repositories.
  • Review every auto-fix diff before considering the lint repair complete.
  • Keep fixes focused on lint compliance and avoid unrelated refactors.

Avoid

  • Do not run npm scripts from untrusted repositories without confirmation.
  • Do not hide type errors by weakening types or disabling rules without approval.
  • Do not continue normal lint repair when secretlint reports exposed credentials.

Frequently Asked Questions

What does this skill run?
It uses the project lint workflow and the documented tools Biome, oxlint, tsgo, and secretlint.
Can it change source files?
Yes. Biome and oxlint can apply automatic fixes, so all diffs should be reviewed.
Does it fix TypeScript errors automatically?
It can help resolve them, but type errors usually require manual reasoning about program behavior.
Does it detect secrets?
It follows the documented secretlint step, which depends on the repository secretlint rules.
Is it safe for untrusted repositories?
Use caution. NPM scripts and workspace binaries can execute code controlled by the repository.
Which assistants can use it?
The report lists support for Claude, Codex, and Claude Code.

Developer Details

Author

yamadashy

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/yamadashy/repomix/tree/main/.claude/skills/lint-fixer

Ref

64ca8af0f54a325752f08bd54e52151061ea659a

Maintenance freshness

7/21/2026

Usage

21 downloads · 231 views

File structure

📄 SKILL.md

More from yamadashy

View all

Related Skills

View all