linting-workflow
When working with code that has linting or type errors, follow this specific workflow: 1. **First attempt automatic fixes**
Install / Use
npx skills add noriaki/re-stock-appInstalls into whichever agent you are using.
.clinerules
Cline rules
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of linting-workflow
linting-workflow scores 51/100 on our quality scale, 2764th of 2,873 Automation skills we index.
Its .clinerules is 1.8 KB long, split into 5 sections and no code examples: moderately detailed.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- Our last check on 2026-10-18 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-23. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
linting-workflow compared with similar skills
All 4 of these similar skills score higher than linting-workflow; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| linting-workflow (this skill)by noriaki | 51 | 0 | — | .clinerules |
| Agent-Reachby Panniantong | 100 | 109.8k | 1d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 99.1k | 1d ago | MCP Server |
| rufloby ruvnet | 100 | 81.1k | today | MCP Server |
| openclawby thedotmack | 100 | 107.6k | 7d ago | SKILL.md |
Frequently asked questions
- How do I install linting-workflow?
- Run
npx skills add noriaki/re-stock-app. The install tabs above show the steps for each supported agent. - Which AI agents does linting-workflow work with?
- It is written for Cline, as a .clinerules file. Other agents that read the same format can often use it too.
- Is linting-workflow safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is linting-workflow still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubLinting and Code Quality Workflow
Process for Handling Code Errors
When working with code that has linting or type errors, follow this specific workflow:
-
First attempt automatic fixes
- Always run
yarn lint:fixbefore manually editing files - For most linting issues, automatic fixes are preferred over manual edits
- Only manually edit files for errors that cannot be automatically fixed
- Always run
-
Handle TypeScript errors
- Run
yarn typecheckto identify type issues - First try resolving errors by using correct types rather than type assertions
- Use proper type narrowing instead of type casting when possible
- Run
-
Verify changes with tests
- After fixing lint/type errors, always run tests with
yarn test - Ensure new fixes don't break existing functionality
- After fixing lint/type errors, always run tests with
-
Complete verification cycle
- Use
yarn checkto run all verification steps in sequence - This combined command ensures all quality checks pass
- Use
When to Try Each Approach
- ESLint errors: Always try
yarn lint:fixfirst - TypeScript errors: Check if they can be resolved with correct typing
- Test failures: Review the test output carefully before making changes
Responding to User Questions
When a user asks you to fix code issues:
- First recommend running the automatic fix: "Let me try running
yarn lint:fixfirst." - If automatic fixes don't resolve all issues, explain: "Some issues require manual fixes. Let me address those now."
- After making changes, always suggest verification: "Let's verify these changes with
yarn check."
Documentation
Always maintain documentation of quality processes:
- Update CLAUDE.md when quality processes change
- Run
yarn build-promptafter adding or modifying .cline/rules/ files - Inform the user of updated quality procedures
Related Skills
Agent-Reach
109.8kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Scrapling
99.1k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
ruflo
81.1k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
openclaw
107.6kThis guide walks through setting up the claude-mem plugin on an OpenClaw gateway. By the end, your agents will have persistent memory across sessions via system prompt context injection, and optionally a real-time observation feed streaming to a messaging channel.
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.