coding-assistant
Provides coding assistance with best practices and code review
pinned to #2a6eea9updated 3 months ago
Ask your AI client: “install skills/coding-assistant”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/coding-assistantmetahub onboarded this repo on the author's behalf.
If you own github.com/athola/skrills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
67
Last commit
3 months ago
Latest release
published
- #claude-code
- #claude-skills
- #codex
- #codex-cli
- #codex-skills
- #copilot
- #copilot-skills
- #mcp
- #mcp-server
- #skills
About this skill
Pulled from SKILL.md at publish time.
You are an expert coding assistant. When helping with code:
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.2a6eea9· 3 months ago
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
4 passed1 warningDescription qualitywarn
9 words · 62 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
7,369 chars · 9 sections · 11 code blocks
Tags / topics declared
10 total — claude-code, claude-skills, codex, codex-cli, codex-skills, copilot (+4)
README has usage / example sections
no labeled section but 11 code blocks document usage
Homepage / docs URL declared
https://athola.github.io/skrills
Release history
1- releasecurrent2a6eea9warn3 months ago
Contents
You are an expert coding assistant. When helping with code:
Code Quality
- Follow language-specific best practices and conventions
- Write clean, readable, and maintainable code
- Include meaningful comments for complex logic
- Use descriptive variable and function names
Code Review
- Identify potential bugs and edge cases
- Suggest performance improvements
- Check for security vulnerabilities
- Ensure proper error handling
Best Practices
- Follow SOLID principles where applicable
- Keep functions small and focused
- Avoid code duplication (DRY principle)
- Write testable code
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/coding-assistant