line-limit
Enforce Code File Line Limits
Large implementation files are hard to review, test, and maintain. This skill checks line counts and guides modular refactoring with clear thresholds.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "line-limit" from https://skillstore.io/skills/doyajin174-line-limit.md and its manifest at https://skillstore.io/api/skills/doyajin174-line-limit/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 "line-limit". Review src/services/api.ts for line limit issues.
Expected outcome:
The file has 342 lines, so it exceeds the 300-line limit. Recommended split: endpoint functions, shared types, and helper utilities.
Using "line-limit". Create a dashboard component and keep it maintainable.
Expected outcome:
The component is approaching the warning threshold. I will separate header, metrics, chart, hooks, and constants before continuing.
Using "line-limit". This utility file is too long. Please organize it.
Expected outcome:
The file should be grouped by responsibility. Suggested modules: string helpers, date helpers, array helpers, and validation helpers.
Security Audit
SafeAll 32 static findings are false positives caused by Markdown backticks and code fences in SKILL.md. The only command shown is a documented, read-only wc line count example, and I found no prompt injection, exfiltration intent, or unsafe automation logic.
Risk Factors
βοΈ External commands (32)
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/doyajin174-line-limit/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/doyajin174-line-limit?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/doyajin174-line-limit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/doyajin174-line-limit/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/doyajin174-line-limit.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
Doyajin174. (2026). line-limit security audit report (audit version 8) [Author version 1.0]. Skillstore. https://skillstore.io/skills/doyajin174-line-limit/audits/8BibTeX citation
@techreport{doyajin174-doyajin174-line-limit-2026,
author = {Doyajin174},
title = {line-limit security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/doyajin174-line-limit/audits/8},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "line-limit security audit report (audit version 8)"
version: "1.0"
type: report
authors:
- name: "Doyajin174"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/doyajin174-line-limit/audits/8"
identifiers:
- type: other
value: "skillstore:doyajin174-line-limit:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Review Oversized Pull Requests
Check changed implementation files and identify modules that should be split before review continues.
Refactor Long Components
Break large UI components into focused files for headers, charts, hooks, types, and constants.
Keep Generated Work Maintainable
Ask the assistant to monitor file length while creating new code and split sections before files become too large.
Try These Prompts
Check the line count for this implementation file and tell me whether it is OK, warning, or violation: [file path].
Review the changed implementation files for line limit issues. Exclude documentation, configuration, generated files, fixtures, and stylesheets.
Analyze [file path], identify logical sections, and propose a modularization plan that keeps each new implementation file under 200 lines.
Refactor [file path] into cohesive modules. Preserve behavior, avoid circular dependencies, update imports, and verify build or tests when possible.
Best Practices
- Check line counts before starting large edits or code review.
- Split code by responsibility, not only by line count.
- Run tests, builds, or lint checks after moving code between files.
Avoid
- Splitting one cohesive function or class only to reduce line count.
- Creating many tiny files that make navigation harder.
- Moving code without updating imports, exports, tests, or public APIs.
Frequently Asked Questions
What files does this skill check?
What line counts are recommended?
Does it apply to documentation?
Can it refactor files automatically?
Does a long file always mean bad code?
Which tools can use this skill?
Developer Details
Author
Doyajin174License
MIT
Author version
v1.0
Skillstore revision
r1
Version notice
The author-declared version is not valid SemVer.
Ref
72d5025b022c77f7a51bdf5c1637c689c80e89d1
Maintenance freshness
7/18/2026
Usage
5 downloads Β· 314 views
File structure