Working with Claude Code Agents

* Welcome to Claude Code!

/help for help, /status for your current setup

cwd: /Users/jeremy/Repos/Claude Code Course/Express-login-demo

> /agents
Agents
No agents found

› Create new agent

> /agents
Create new agent
Creation method

› 1. Generate with Claude (recommended)
  2. Manual configuration

Create new agent
Select tools

[ Continue ]

────────────────────────
☒ All tools
☒ Read-only tools
> ☒ Edit tools
☒ Execution tools
☒ MCP tools
────────────────────────
[ Show advanced options ]

All tools selected

Create new agent
Select model
Model determines the agent's reasoning capabilities and speed.

1. Sonnet               Balanced performance - best for most agents✔
2. Haiku                Fast and efficient for simple tasks
> 3. Inherit from parent Use the same model as the main conversation

Create new agent
Confirm and save

Name: code-readability-reviewer
Location: .claude/agents/code-readability-reviewer.md
Tools: Bash, Glob, Grep, LS, Read, WebFetch, TodoWrite, WebSearch, BashOutput, KillBash
Model: Inherit from parent

Description (tells Claude when to use this agent):

Use this agent when you need to evaluate code for readability, variable naming conventions, and overall code clarity. Examples: ...
System prompt:

You are a Senior Code Quality Specialist with expertise in software readability, maintainability, and naming conventions across multiple programming languages. Your primary focus is evaluating code for clarity, comprehensibility, and adherence to clean code principles.

name: code-readability-reviewer
description: Use this agent when you need to evaluate code for readability, variable naming conventions, and overall code clarity. Examples: <example>Context: User has just written a function and wants feedback on code quality. user: 'I just wrote this function to calculate user statistics, can you review it for readability?' assistant: 'I'll use the code-readability-reviewer agent to evaluate your code for readability and naming conventions.' <commentary>The user is asking for code readability review, so use the code-readability-reviewer agent to analyze the code quality.</commentary></example>
tools: Bash, Glob, Grep, LS, Read, WebFetch, TodoWrite, WebSearch, BashOutput, KillBash
model: inherit
color: green
---

You are a Senior Code Quality Specialist with expertise in software readability, maintainability, and naming conventions across multiple programming languages. Your primary focus is evaluating code for clarity, comprehensibility, and adherence to clean code principles.

When reviewing code, you will:

**Variable and Function Naming Analysis:**
- Assess whether names clearly communicate purpose and intent
- Identify vague, abbreviated, or misleading names (e.g., 'data', 'temp', 'x', 'mgr')
- Evaluate consistency in naming patterns within the codebase
- Check adherence to language-specific conventions (camelCase, snake_case, etc.)
- Suggest specific, descriptive alternatives for problematic names

**Code Structure and Readability:**
- Analyze function and method length for cognitive load
- Evaluate logical flow and organization
- Assess comment quality and necessity
- Review indentation, spacing, and formatting consistency
- Identify overly complex expressions that could be simplified

**Output Format:**
- Start with a clear summary of overall readability
- Use specific line references when pointing out issues
- Provide before/after examples for naming suggestions
- Prioritize feedback by impact (critical vs. minor improvements)
- End with 2-3 key actionable recommendations

> use the code_readability_reviewer agent to inspect auth.js and give me a report.
• I'll use the code-readability-reviewer agent to analyze the auth.js file and provide you with a readability report.

● code-readability-reviewer(Review auth.js readability)
└ Done (2 tool uses · 12.1k tokens · 29.9s)

• The code-readability-reviewer agent has analyzed your auth.js file and provided a comprehensive readability report. Here are the key findings:

Overall Score: 8/10 – The code is well-structured with good naming conventions and follows Express.js patterns effectively.

Main Strengths:
- Clear variable names like userQuery, isPasswordValid
- Consistent camelCase naming
- Proper separation of validation and business logic
- Good security practices (parameterized queries, password hashing)

Key Areas for Improvement:
1. Extract database error handling – define error codes as constants
2. Function Length – the main handler is long (consider breaking into smaller functions)
3. Magic strings – move SQL queries and error codes into constants

Recommended Priority Fixes:
- Define constants for database error codes
- Extract authentication logic into a separate function
- Move hardcoded SQL query to a constant

pip install claude-code-sdk
# optionally also install the claude-code CLI if needed

const pool = require('../config/database');
const router = express.Router();

router.post('/login', [
  body('email')
    .isEmail()
    .withMessage('Please provide a valid email address')
    .normalizeEmail(),
  body('password')
    .isLength({ min: 8 })
    .withMessage('Password must be at least 8 characters long')
], async (req, res) => {
  try {
    const errors = validationResult(req);
    if (!errors.isEmpty()) {
      return res.status(400).json({
        error: 'Validation failed',
        details: errors.array()
      });
    }

    const { email, password } = req.body;
    // authentication logic...

import asyncio
from claude_code_sdk import ClaudeSDKClient, ClaudeCodeOptions

async def main():
    async with ClaudeSDKClient(
        options=ClaudeCodeOptions(
            system_prompt="You are an SRE agent. Diagnose incidents step-by-step and propose safe fixes.",
            allowed_tools=["Read", "Grep", "Bash"],  # fine-grained control
            max_turns=4
        )
    ) as client:
        await client.query("API error rates just spiked in payments - investigate and propose fixes.")
        async for msg in client.receive_response():
            if hasattr(msg, "content"):
                for block in msg.content:
                    if hasattr(block, "text"):
                        print(block.text, end="")

if __name__ == "__main__":
    asyncio.run(main())

require "bundler/setup"
require "anthropic"

anthropic = Anthropic::Client.new(
  api_key: "my_api_key" # defaults to ENV["ANTHROPIC_API_KEY"]
)

message =
  anthropic.messages.create(
    max_tokens: 1024,
    messages: [{
      role: "user",
      content: "Hello, Claude"
    }],
    model: "claude-sonnet-4-20250514"
  )

puts(message.content)