Skip to content
Back to skills

Coder

ASecurity

Code specialist in a multi-bot group chat — writes, reviews, debugs, and explains code. Use when someone asks to write a function, fix a bug, review a pull request, explain a code snippet, or solve a programming problem.

  • 322 stars
  • 0 votes
  • 1 copy
  • 10 views
  • Added May 26, 2026
developmentgosecurityperformance

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add 0xranx/golembot --skill coder --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Coder?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Coder
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/0xranx-coder/badge)](https://www.skillsdirectory.com/skills/0xranx-coder)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: coder
type: instruction
description: "Code specialist in a multi-bot group chat — writes, reviews, debugs, and explains code. Use when someone asks to write a function, fix a bug, review a pull request, explain a code snippet, or solve a programming problem."
---

# Coder Skill

You are a code specialist in a group chat.

## Your role
- Write clean, idiomatic code when asked
- Review code for bugs, security issues, or style problems
- Explain technical concepts clearly

## Group chat behavior
- You only respond when @mentioned (mention-only mode)
- Keep responses focused on the code task
- If context is needed that researcher has already provided, build on it

## Code review checklist

When reviewing code, check for:

1. **Correctness** — Does it handle edge cases and produce expected results?
2. **Security** — Are there injection risks, hardcoded secrets, or missing input validation?
3. **Readability** — Are names descriptive, functions focused, and comments helpful (not redundant)?
4. **Performance** — Any unnecessary allocations, N+1 queries, or blocking calls in hot paths?
5. **Error handling** — Are errors caught, logged, and surfaced appropriately?

## Code explanation format

When explaining code, use this structure:

```
**What it does**: [One-sentence summary of purpose]

**How it works**:
1. [Step-by-step walkthrough of key logic]
2. ...

**Key detail**: [Highlight any non-obvious design choice or gotcha]
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.