run-linters
Run Linters After Code Changes
Code changes often introduce lint errors that slow reviews and releases. This skill runs configured linters and guides fixes until the checks pass.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "run-linters" from https://skillstore.io/skills/cloud-officer-run-linters.md and its manifest at https://skillstore.io/api/skills/cloud-officer-run-linters/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.
Test it
Using "run-linters". Run lint checks after updating the authentication files.
Expected outcome:
The lint run found style issues in two changed files. I fixed them and confirmed the next lint run passed.
Using "run-linters". Check whether my refactor is ready for review.
Expected outcome:
The repository linters completed successfully. No lint changes are needed before review.
Using "run-linters". Fix the lint failures from my latest changes.
Expected outcome:
I fixed the reported unused import and formatting issues. One rule change looked project-specific, so I asked before modifying it.
Security Audit
SafeThe three static findings are false positives caused by Markdown backticks around the command and fenced code block in SKILL.md. The skill directs the assistant to run a single lint command through the declared allowed tool, and no prompt injection or data exfiltration intent was found.
Risk Factors
⚙️ External commands (3)
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.
Copy report link
https://skillstore.io/skills/cloud-officer-run-linters/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cloud-officer-run-linters?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cloud-officer-run-linters?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cloud-officer-run-linters/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cloud-officer-run-linters.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
Cloud-Officer. (2026). run-linters security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cloud-officer-run-linters/audits/9BibTeX citation
@techreport{cloud-officer-cloud-officer-run-linters-2026,
author = {Cloud-Officer},
title = {run-linters security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/cloud-officer-run-linters/audits/9},
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: "run-linters security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "Cloud-Officer"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/cloud-officer-run-linters/audits/9"
identifiers:
- type: other
value: "skillstore:cloud-officer-run-linters:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare a Pull Request
Run linters after a feature branch is ready and fix issues before review.
Clean Up Refactors
Check formatting and style after broad edits that touched multiple files.
Verify Agent Changes
Confirm AI-assisted edits still meet repository lint standards before handoff.
Try These Prompts
Run the lint checks for this repository and tell me whether anything needs to be fixed.
Run the linters, fix any reported issues, and re-run the checks until they pass.
After my recent changes, run the configured linters and resolve blocking lint errors before I open a pull request.
Run the linters, group failures by cause, fix clear issues, and ask before changing any lint rule or project convention.
Best Practices
- Run this skill after a complete set of related code changes.
- Review any proposed lint rule changes before accepting them.
- Pair lint checks with tests or builds when release confidence matters.
Avoid
- Do not run linters after every tiny edit in an active coding loop.
- Do not disable lint rules just to make the check pass.
- Do not treat a clean lint result as proof that behavior is correct.
Frequently Asked Questions
What command does this skill run?
When should I use this skill?
Will it fix lint issues automatically?
Does it run tests too?
Can it change lint rules?
Which assistants can use it?
Developer Details
Author
Cloud-OfficerLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
02f077c174c5335e2f5d02ca15e77b70d9543e58
Maintenance freshness
7/18/2026
Usage
6 downloads · 173 views
File structure
📄 SKILL.md