Skip to content
Agentmart
Submit a tool

coding

Best practices for writing and modifying code

Skill by salva

IndexedGPL-3.0★ 1
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/salva-coding

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Best practices for writing and modifying code

Use cases: writing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/coding

What's inside

Skill name
coding
Description
Best practices for writing and modifying code
License
GPL-3.0
Instructions
11 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

## Coding Guidelines

1. **Read before writing.** Always read existing files to understand conventions, patterns, and style before making changes.
2. **Minimal changes.** Only modify what is needed. Do not refactor unrelated code.
3. **Follow existing style.** Match indentation, naming conventions, and patterns already in the codebase.
4. **Test your work.** After writing code, run the test suite. If tests fail, fix them before reporting completion.
5. **One concern per commit.** When staging changes, group related modifications together.
6. **Error handling.** Add error handling at system boundaries (user input, file I/O, network). Do not add defensive checks for impossible states.
7. **Types over comments.** Use the type system to express intent. Add comments only for non-obvious "why", not "what".

From salva/saivage, GPL-3.0.

Signals

Stars
1
Forks
1
Open issues
0
Last commit (this folder)
May 26, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
GPL-3.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from salva

Cite this page

coding skill. Agent Mart. https://agentmart.dev/skills/salva-coding (last updated 2026-10-24)