FI

fix-common-issues

Automatically remediates mechanical errors in codebase files before plugin validation.

Install

mkdir -p .claude/skills/fix-common-issues && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11378" && unzip -o skill.zip -d .claude/skills/fix-common-issues && rm skill.zip

Installs to .claude/skills/fix-common-issues

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Automatically fixes mechanical issues found during plugin validation, including JSON formatting, missing shebangs, file permissions, hook types, frontmatter gaps, and settings.json defaults. ALWAYS asks for confirmation before modifying any files. Trigger: fix issues, auto-fix, fix common problems, repair plugin.
314 charsno explicit “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Beginner

Key capabilities

  • →Detect and plan fixes for JSON trailing commas and indentation
  • →Detect and plan fixes for missing shebangs in shell scripts
  • →Detect and plan fixes for non-executable script permissions
  • →Detect and plan fixes for incompatible hook types in `hooks.json`
  • →Detect and plan fixes for missing frontmatter fields in `SKILL.md`

How it works

The skill inventories mechanical issues, plans specific fixes for each, presents these plans to the user for approval, applies the approved changes, and then re-validates the modified files.

Inputs & outputs

You give it
Plugin validation findings or files with common mechanical issues
You get back
A numbered list of proposed file modifications for user approval, followed by applied fixes and a report

When to use fix-common-issues

  • →Fixing JSON syntax errors
  • →Adding missing shebangs to scripts
  • →Correcting file permissions

About fix-common-issues

Detects and fixes formatting errors, including JSON indentation, missing script headers, and incorrect file permissions. Always requests user approval before applying changes.

>

When not to use it

  • →When fixing semantic issues that require human judgment
  • →When the user has not approved the proposed changes
  • →When the goal is to undo applied fixes

Limitations

  • →Cannot fix semantic issues
  • →Requires explicit user confirmation before modifying files
  • →Cannot undo applied fixes

How it compares

This skill automates the detection and proposed remediation of common mechanical code issues, requiring explicit user approval before any file modification, unlike manual code review or silent auto-formatting.

Compared to similar skills

fix-common-issues side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
fix-common-issues (this skill)07moNo flagsBeginner
n8n-expression-syntax67moNo flagsBeginner
python-repl67moReviewBeginner
n8n-validation-expert67moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

n8n-expression-syntax

czlonkowski

Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.

6111

python-repl

gptme

Interactive Python REPL automation with common helpers and best practices

6102

n8n-validation-expert

czlonkowski

Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, or the validation loop process.

697

powershell-windows

davila7

PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.

2379

bats

OleksandrKucherenko

Bash Automated Testing System (BATS) for TDD-style testing of shell scripts. Use when: (1) Writing unit or integration tests for Bash scripts, (2) Testing CLI tools or shell functions, (3) Setting up test infrastructure with setup/teardown hooks, (4) Mocking external commands (curl, git, docker), (5) Generating JUnit reports for CI/CD, (6) Debugging test failures or flaky tests, (7) Implementing test-driven development for shell scripts.

991

browser-daemon

noiv

Persistent browser automation via Playwright daemon. Keep a browser window open and send it commands (navigate, execute JS, inspect console). Perfect for interactive debugging, development, and testing web applications. Use when you need to interact with a browser repeatedly without opening/closing it.

587

Search skills

Search the agent skills registry