skills.rest
COLDTURNIP
COLDTURNIPCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ascii-scanner

Scan files for non-ASCII characters and report violations with paths and line numbers.

Updated Jan 19, 2026
Search Tags:#validation#repository#pre-commit#grep#lint#ascii#non-ascii
One-click install
npx skills add https://github.com/COLDTURNIP/longhorn-workspace --skill ascii-scanner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ascii-scanner
Source: https://github.com/COLDTURNIP/longhorn-workspace/tree/main/.opencode/skills/ascii-scanner
Command: npx skills add https://github.com/COLDTURNIP/longhorn-workspace --skill ascii-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces workspace-wide ASCII-only compliance to prevent cross-platform issues and repository hygiene by scanning for non-ASCII characters, emojis, and smart quotes.

Core Features & Use Cases

  • Workspace-wide validation: Detects non-ASCII characters across the repository to ensure portability and consistency.
  • Targeted scanning: Focuses on changed files or specified paths to minimize overhead during development.
  • CI/CD integration: Can be integrated into pre-commit hooks or pipelines to fail builds on violations.

Quick Start

Run the scanner from the workspace root to check specific files or directories: bash .opencode/skills/ascii-scanner/ascii_scanner.sh "repo/<repo-name>/path/to/file"

Frequently Asked Questions about ascii-scanner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my repository for non-ASCII characters before committing?▼

To check your repository for non-ASCII characters, you can run a scanner script that uses standard Unix tools like grep to identify violations across files or directories, emitting file paths and line numbers to support pre-commit checks.

Can I scan only changed files for non-ASCII characters in a CI pipeline?▼

Yes, you can scan only changed files for non-ASCII characters in a CI pipeline by passing specific file paths as arguments to the scanner script, minimizing overhead during development and post-generation validations.

What is the best way to enforce ASCII-only code in a workspace?▼

The best way to enforce ASCII-only code in a workspace is to integrate a validation scanner into CI CD pipelines or pre-commit hooks, which will fail builds and report violations containing file paths and line numbers when non-ASCII characters are detected.

Does this non-ASCII scanner require any external dependencies?▼

No, this non-ASCII scanner does not require external dependencies because it relies solely on Bash and standard Unix tools like grep to perform workspace-wide validation and report violations.

Why should I lint my codebase for smart quotes and emojis?▼

You should lint your codebase for smart quotes and emojis to prevent cross-platform issues and maintain repository hygiene, ensuring portability and consistency by enforcing strict ASCII-only compliance across your workspace.

Related Skills

Explore More Software Engineering Skills→
matteotittamatteotitta
29

why-slow

Diagnose performance bottlenecks in Claude Code sessions from process logs and MCP health.

Community
Intermediate
SumitRajpalSumitRajpal

check-theme

Audit React/Next.js frontend code for hardcoded theme token violations.

Community
Intermediate
pcasarettopcasaretto

lint

Lint Ruby and ERB files with standardrb, erblint, and brakeman.

Community
Intermediate
nopperabbonopperabbo
7

bash-script-validator

Validate Bash and POSIX sh scripts with syntax and ShellCheck analysis.

Community
Advanced