Common questions about Claude Code Tresor.
Claude Code Tresor is a comprehensive collection of professional-grade utilities for Claude Code CLI, including:
- 8 Autonomous Skills - Automatic background helpers (code-reviewer, security-auditor, etc.)
- 8 Specialized Agents - Expert sub-agents for deep analysis (@config-safety-reviewer, @test-engineer, etc.)
- 4 Essential Commands - Workflow automation (/scaffold, /review, /test-gen, /docs-gen)
- 20+ Prompt Templates - Production-ready prompts for common scenarios
- Development Standards - Style guides, Git workflows, collaboration guidelines
Think of it as: A professional toolkit that augments Claude Code with specialized experts and automation.
Author: Alireza Rezvani License: MIT Repository: https://github.com/alirezarezvani/claude-code-tresor Contact: rezvani@gmail.com
Yes! Claude Code Tresor is open source under the MIT License:
- ✅ Free for personal use
- ✅ Free for commercial use
- ✅ No attribution required (but appreciated!)
- ✅ Modify and redistribute freely
| Feature | Skills | Agents | Commands |
|---|---|---|---|
| Invocation | Automatic | Manual (@agent) |
Manual (/command) |
| When to use | Continuous monitoring | Deep analysis | Workflows |
| Tool access | Limited (safe) | Full access | Orchestrates |
| Context | Shared | Separate | Coordinates |
| Examples | code-reviewer (skill) | @config-safety-reviewer (agent) | /review (command) |
Simple explanation:
- Skills = Automatic helpers (always watching)
- Agents = Expert consultants (call when needed)
- Commands = Workflow automation (multi-step processes)
Use Skills when:
- ✅ You want automatic, continuous monitoring
- ✅ You need real-time suggestions while coding
- ✅ You want lightweight, non-blocking feedback
Example: Let code-reviewer skill monitor your code as you work.
Use Agents when:
- ✅ You need deep, comprehensive analysis
- ✅ You have a specific complex question
- ✅ You need expert guidance on architecture/design
- ✅ You're debugging a complex issue
Example: @systems-architect design a scalable microservices architecture
Use Commands when:
- ✅ You need to automate a multi-step workflow
- ✅ You want to coordinate multiple agents
- ✅ You're running a standardized process (scaffolding, review, testing)
Example: /review --scope all --checks security,performance
Skills are conversation-based autonomous helpers that activate automatically:
How they activate:
- You save a file with code changes
- Skill detects the change (based on file patterns)
- Skill analyzes the code
- Skill provides suggestions in conversation
Example:
You: [Saves UserProfile.tsx with missing error handling]
code-reviewer skill: "⚠️ Missing error handling in async function.
Suggestion: Add try-catch block to handle API failures."
Key points:
- ✅ NO manual invocation needed
- ✅ Works in background continuously
- ✅ Provides suggestions without interrupting
- ✅ Limited tool access for safety
Use @agent-name syntax:
@config-safety-reviewer analyze src/api/users.controller.ts for security issues
Tips for better results:
- Be specific about what you want
- Provide context (production, requirements, constraints)
- Specify focus areas
Example:
@systems-architect design user authentication system
Requirements:
- 10k concurrent users
- JWT tokens
- Refresh token mechanism
- Rate limiting
Constraints:
- Node.js/Express
- PostgreSQL
- 2-week timeline
Use /command-name syntax with options:
/review --scope staged --checks security,performance
Get help:
/review --help
Common commands:
# Scaffold components
/scaffold react-component UserProfile --typescript --tests
# Code review
/review --scope all --checks all
# Generate tests
/test-gen --file src/utils/helpers.ts --coverage 90
# Generate documentation
/docs-gen api --format openapiFull installation (recommended):
git clone https://github.com/alirezarezvani/claude-code-tresor.git
cd claude-code-tresor
./scripts/install.shSelective installation:
./scripts/install.sh --skills # 8 skills only
./scripts/install.sh --agents # 8 agents only
./scripts/install.sh --commands # 4 commands only- Skills:
~/.claude/skills/ - Agents:
~/.claude/agents/ - Commands:
~/.claude/commands/ - Prompts:
~/.claude/prompts/ - Standards:
~/.claude/standards/
Repository stays separate at ~/claude-code-tresor/ (or wherever you cloned it).
Yes, recommended for:
- Updates (
git pull && ./scripts/update.sh) - Reference documentation
- Examples and templates
But not required - installed utilities work independently.
cd claude-code-tresor
git pull origin main
./scripts/update.shPreserves your customizations while updating utilities.
Yes:
# Remove all components
rm -rf ~/.claude/skills/code-reviewer
rm -rf ~/.claude/skills/test-generator
# ... (remove all skills)
rm -rf ~/.claude/agents/code-reviewer
# ... (remove all agents)
rm -rf ~/.claude/commands/scaffold
# ... (remove all commands)
# Remove repository
rm -rf ~/claude-code-tresorComplete uninstall instructions →
Yes! Edit configuration files:
Skills:
vi ~/.claude/skills/code-reviewer/SKILL.md
# Edit YAML frontmatterAgents:
vi ~/.claude/agents/code-reviewer/SKILL.md
# Edit YAML frontmatterCommands:
vi ~/.claude/commands/review/command.json
# Edit JSON configurationComplete configuration guide →
Absolutely! Follow our guides:
Yes, set enabled: false in skill configuration:
---
name: "readme-updater"
enabled: false # Skill disabled
---Restart Claude Code for changes to take effect.
Edit skill's YAML frontmatter:
---
name: "code-reviewer"
file_patterns:
- "src/**/*.ts" # Only TypeScript in src/
- "src/**/*.tsx"
exclude_patterns:
- "*.test.*" # Exclude tests
- "*.stories.*" # Exclude Storybook
- "node_modules/**" # Exclude dependencies
---Common causes:
- Skill disabled:
---
enabled: false # Change to true
---- File patterns don't match:
---
file_patterns:
- "*.ts" # Does this match your files?
---- File excluded:
---
exclude_patterns:
- "node_modules/**" # Is your file here?
---- Need to restart: Restart Claude Code CLI
Solutions:
# 1. Check agent exists
ls ~/.claude/agents/code-reviewer/
# 2. Verify configuration
cat ~/.claude/agents/code-reviewer/SKILL.md
# 3. Check enabled field
---
enabled: true # Must be true
---
# 4. Restart Claude CodeSolutions:
# 1. Check command exists
ls ~/.claude/commands/review/
# 2. Verify configuration
cat ~/.claude/commands/review/command.json
# 3. Try full path
/workflow/review # Instead of /review
# 4. Check syntax
/review --help # Show correct usage
# 5. Restart Claude CodeOption 1: Lower priority:
---
name: "code-reviewer"
priority: "low" # Changed from "high"
---Option 2: Disable temporarily:
---
name: "readme-updater"
enabled: false
---Option 3: Narrow scope:
---
name: "test-generator"
file_patterns:
- "src/**/*.ts" # Only src/ directory
exclude_patterns:
- "*.test.*" # Exclude existing tests
---Major changes:
- NEW: 8 autonomous skills
- CHANGED: Agent syntax (
rr-→@) - CHANGED: Directory structure
Migration steps:
cd claude-code-tresor
git pull origin main
./scripts/migrate-v1-to-v2.shv1.0 (old):
rr-code-reviewer analyze this
v2.0 (new):
@config-safety-reviewer analyze this
No - skills are lightweight:
- Limited tool access (Read, Write, Edit, Grep, Glob only)
- Efficient conversation-based activation
- Run in background without blocking
If experiencing slowness:
- Reduce active skills (disable non-essential)
- Narrow file patterns (monitor fewer files)
- Use Sonnet model instead of Opus for skills
No hard limit, but practical recommendations:
- Skills: 5-10 active skills (more = more suggestions)
- Agents: Unlimited (invoked manually as needed)
- Commands: Unlimited
Balance: More skills = more feedback but potentially overwhelming.
Generally no - commands orchestrate workflows sequentially.
Exception: If commands are independent (different scopes).
Recommendation: Run commands one at a time for best results.
Ways to contribute:
- Report bugs - GitHub Issues →
- Suggest features - GitHub Discussions →
- Create skills/agents/commands - Contributing Guide →
- Improve documentation - Submit PRs for documentation
- Share prompts/templates - Contribute useful patterns
- Review PRs - Help review community contributions
Resources:
- Troubleshooting Guide → - Fix common issues
- This FAQ → - Quick answers
- GitHub Discussions → - Ask questions
- GitHub Issues → - Report bugs
Yes!
- GitHub Discussions → - Community forum
- Contributors → - Meet the community
Yes, through coordination configuration:
---
name: "code-reviewer"
coordination:
invoke_agents:
- agent: "@security-auditor"
when: "security_issue_detected"
---Future feature - currently skills suggest agent invocation to user.
Yes, using the Task tool:
@systems-architect design system
[Invokes @security-auditor for security review]
[Invokes @performance-tuner for optimization]
Yes! Claude Code Tresor is designed to work alongside:
- Other skills
- Other agents
- Other commands
- MCP servers
Potential conflicts:
- Skills with similar names (ensure unique names)
- Commands with same name (use unique names)
Partially:
- ✅ Configuration and documentation accessible offline
- ✅ Templates and standards available offline
- ❌ Skills/agents/commands require Claude AI (online)
Can't find your answer?
- Search Documentation → - Browse complete docs
- Ask Community → - Post question
- Report Issue → - If you found a bug
Last Updated: November 7, 2025 | Version: 2.0.0