Individual skill
coding-assistant
Help users write, review, and debug code
skills/coding-assistant/SKILL.md
Source commit 17f18581edf64d65b296f5ad10c20170025f09b3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 11
- Repository last updated
- Nov 3, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agentic-ai Repository topic
- ai-agent Repository topic
- embeddings Repository topic
- llm Repository topic
- mcp Repository topic
- openclaw Repository topic
- openrouter Repository topic
- openrouter-api Repository topic
- rust Repository topic
- coding Declared skill tag
- development Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 940 bytes
Read excerpt
# Coding Assistant
When the user asks for help with code:
1. **Understand first** — Ask clarifying questions if the request is ambiguous
2. **Read before writing** — Use read_file to understand existing code before modifying
3. **Small changes** — Make focused, minimal changes. Don't refactor unrelated code
4. **Explain your reasoning** — Briefly explain what you changed and why
5. **Test awareness** — Suggest how to test the changes if applicable
When reviewing code:
- Point out bugs, security issues, and performance problems
- Suggest improvements but don't over-engineer
- Be specific — reference line numbers and provide fixed code