Enforcing Typescript Standards
CheckedAutomatically flags and corrects TypeScript code to adhere to project-specific linting rules and best practices.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add jgeurts/oxlint-config-decent --skill enforcing-typescript-standards -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
jgeurts
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned jgeurts/eslint-config-decent at 1f750d7b3a.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1f750d7b3a
- Scanned
- 1 file, 393 lines
About this skill
The enforcing-typescript-standards skill integrates the eslint-config-decent configuration to automatically validate and correct TypeScript code against industry best practices. It ensures consistency across your backend projects by applying strict linting rules directly within your development workflow.
When to use it
- Standardizing new TypeScript repositories to prevent common coding errors from the start.
- Running automated checks in CI/CD pipelines to block non-compliant code merges.
- Refactoring legacy TypeScript codebases to align with modern, secure standards.
- Enforcing strict type safety and naming conventions across large teams.
Key capabilities
- Applies the
eslint-config-decentrule set specifically tailored for TypeScript environments. - Detects and reports violations of established backend coding standards.
- Provides actionable feedback to developers regarding syntax and structural issues.
Example prompts
- "Analyze my current TypeScript project structure and apply the decent ESLint configuration to identify any standard violations."
- "Generate a script that runs
eslint-config-decenton all files in the backend directory and outputs a summary of errors." - "Refactor this specific TypeScript module to comply with the strict typing and formatting rules defined in the decent config."
Tips & gotchas
- Prerequisites include having Node.js installed and an existing TypeScript project setup.
- This skill focuses on static analysis; it does not execute code or fix runtime logic errors, only style and type inconsistencies.