On Edit Formatter
Apply code formatting rules after file edits in the source directory. Use when asked to format code or after making changes to source files.
Install
$ agentstack add skill-davila7-claude-with-skills-on-edit-formatter ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-davila7-claude-with-skills-on-edit-formatter) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Post-edit formatting
After making any file edit in src/ or lib/, apply formatting automatically. This skill runs as background context — Claude applies these rules after edits without the user needing to ask.
Step 1: Run prettier on the edited file
Run:
npx prettier --write Replace `` with the actual path of the file that was just edited.
If prettier modifies the file, note what changed (e.g., "Reformatted 3 lines in src/auth/login.ts").
If prettier is not installed or not configured (no .prettierrc, prettier.config.js, or prettier key in package.json), skip this step and note: "prettier not configured in this project."
Step 2: Run eslint --fix on the edited file
Run:
npx eslint --fix Replace `` with the same path.
If eslint --fix makes changes, note what was fixed.
If eslint reports errors that --fix cannot resolve automatically, list them clearly so the user is aware. Do not hide linting errors.
If eslint is not installed or not configured (no .eslintrc*, eslint.config.*, or eslintConfig key in package.json), skip this step and note: "eslint not configured in this project."
Step 3: Report
Summarize what was done:
- Which file was formatted
- What prettier changed (or that it made no changes)
- What eslint fixed (or that it made no changes)
- Any remaining eslint errors requiring manual attention
If neither tool is installed, report that and do not treat it as an error. The task proceeds normally.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: davila7
- Source: davila7/claude-with-skills
- License: MIT
- Homepage: https://claude-with-skills.vercel.app
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.