bobo-ai-cli 1.0.2 → 1.2.0

package/bundled-skills/canvas-design/SKILL.md

@@ -0,0 +1,147 @@
+---
+id: "canvas-design"
+title: "Canvas Design"
+category: "design"
+tags: ["design philosophy creation", "deducing the subtle reference", "canvas creation", "final step", "multi-page option"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/canvas-design"
+---
+
+---
+name: canvas-design
+description: Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
+license: Complete terms in LICENSE.txt
+---
+
+These are instructions for creating design philosophies - aesthetic movements that are then EXPRESSED VISUALLY. Output only .md files, .pdf files, and .png files.
+
+Complete this in two steps:
+
+1. Design Philosophy Creation (.md file)
+2. Express by creating it on a canvas (.pdf file or .png file)
+
+First, undertake this task:
+
+## DESIGN PHILOSOPHY CREATION
+
+To begin, create a VISUAL PHILOSOPHY (not layouts or templates) that will be interpreted through:
+
+- Form, space, color, composition
+- Images, graphics, shapes, patterns
+- Minimal text as visual accent
+
+### THE CRITICAL UNDERSTANDING
+
+- What is received: Some subtle input or instructions by the user that should be taken into account, but used as a foundation; it should not constrain creative freedom.
+- What is created: A design philosophy/aesthetic movement.
+- What happens next: Then, the same version receives the philosophy and EXPRESSES IT VISUALLY - creating artifacts that are 90% visual design, 10% essential text.
+
+Consider this approach:
+
+- Write a manifesto for an art movement
+- The next phase involves making the artwork
+
+The philosophy must emphasize: Visual expression. Spatial communication. Artistic interpretation. Minimal words.
+
+### HOW TO GENERATE A VISUAL PHILOSOPHY
+
+**Name the movement** (1-2 words): "Brutalist Joy" / "Chromatic Silence" / "Metabolist Dreams"
+
+**Articulate the philosophy** (4-6 paragraphs - concise but complete):
+
+To capture the VISUAL essence, express how the philosophy manifests through:
+
+- Space and form
+- Color and material
+- Scale and rhythm
+- Composition and balance
+- Visual hierarchy
+
+**CRITICAL GUIDELINES:**
+
+- **Avoid redundancy**: Each design aspect should be mentioned once. Avoid repeating points about color theory, spatial relationships, or typographic principles unless adding new depth.
+- **Emphasize craftsmanship REPEATEDLY**: The philosophy MUST stress multiple times that the final work should appear as though it took countless hours to create, was labored over with care, and comes from someone at the absolute top of their field. This framing is essential - repeat phrases like "meticulously crafted," "the product of deep expertise," "painstaking attention," "master-level execution."
+- **Leave creative space**: Remain specific about the aesthetic direction, but concise enough that the next Claude has room to make interpretive choices also at a extremely high level of craftmanship.
+
+The philosophy must guide the next version to express ideas VISUALLY, not through text. Information lives in design, not paragraphs.
+
+### PHILOSOPHY EXAMPLES
+
+**"Concrete Poetry"**
+Philosophy: Communication through monumental form and bold geometry.
+Visual expression: Massive color blocks, sculptural typography (huge single words, tiny labels), Brutalist spatial divisions, Polish poster energy meets Le Corbusier. Ideas expressed through visual weight and spatial tension, not explanation. Text as rare, powerful gesture - never paragraphs, only essential words integrated into the visual architecture. Every element placed with the precision of a master craftsman.
+
+**"Chromatic Language"**
+Philosophy: Color as the primary information system.
+Visual expression: Geometric precision where color zones create meaning. Typography minimal - small sans-serif labels letting chromatic fields communicate. Think Josef Albers' interaction meets data visualization. Information encoded spatially and chromatically. Words only to anchor what color already shows. The result of painstaking chromatic calibration.
+
+**"Analog Meditation"**
+Philosophy: Quiet visual contemplation through texture and breathing room.
+Visual expression: Paper grain, ink bleeds, vast negative space. Photography and illustration dominate. Typography whispered (small, restrained, serving the visual). Japanese photobook aesthetic. Images breathe across pages. Text appears sparingly - short phrases, never explanatory blocks. Each composition balanced with the care of a meditation practice.
+
+**"Organic Systems"**
+Philosophy: Natural clustering and modular growth patterns.
+Visual expression: Rounded forms, organic arrangements, color from nature through architecture. Information shown through visual diagrams, spatial relationships, iconography. Text only for key labels floating in space. The composition tells the story through expert spatial orchestration.
+
+**"Geometric Silence"**
+Philosophy: Pure order and restraint.
+Visual expression: Grid-based precision, bold photography or stark graphics, dramatic negative space. Typography precise but minimal - small essential text, large quiet zones. Swiss formalism meets Brutalist material honesty. Structure communicates, not words. Every alignment the work of countless refinements.
+
+_These are condensed examples. The actual design philosophy should be 4-6 substantial paragraphs._
+
+### ESSENTIAL PRINCIPLES
+
+- **VISUAL PHILOSOPHY**: Create an aesthetic worldview to be expressed through design
+- **MINIMAL TEXT**: Always emphasize that text is sparse, essential-only, integrated as visual element - never lengthy
+- **SPATIAL EXPRESSION**: Ideas communicate through space, form, color, composition - not paragraphs
+- **ARTISTIC FREEDOM**: The next Claude interprets the philosophy visually - provide creative room
+- **PURE DESIGN**: This is about making ART OBJECTS, not documents with decoration
+- **EXPERT CRAFTSMANSHIP**: Repeatedly emphasize the final work must look meticulously crafted, labored over with care, the product of countless hours by someone at the top of their field
+
+**The design philosophy should be 4-6 paragraphs long.** Fill it with poetic design philosophy that brings together the core vision. Avoid repeating the same points. Keep the design philosophy generic without mentioning the intention of the art, as if it can be used wherever. Output the design philosophy as a .md file.
+
+---
+
+## DEDUCING THE SUBTLE REFERENCE
+
+**CRITICAL STEP**: Before creating the canvas, identify the subtle conceptual thread from the original request.
+
+**THE ESSENTIAL PRINCIPLE**:
+The topic is a **subtle, niche reference embedded within the art itself** - not always literal, always sophisticated. Someone familiar with the subject should feel it intuitively, while others simply experience a masterful abstract composition. The design philosophy provides the aesthetic language. The deduced topic provides the soul - the quiet conceptual DNA woven invisibly into form, color, and composition.
+
+This is **VERY IMPORTANT**: The reference must be refined so it enhances the work's depth without announcing itself. Think like a jazz musician quoting another song - only those who know will catch it, but everyone appreciates the music.
+
+---
+
+## CANVAS CREATION
+
+With both the philosophy and the conceptual framework established, express it on a canvas. Take a moment to gather thoughts and clear the mind. Use the design philosophy created and the instructions below to craft a masterpiece, embodying all aspects of the philosophy with expert craftsmanship.
+
+**IMPORTANT**: For any type of content, even if the user requests something for a movie/game/book, the approach should still be sophisticated. Never lose sight of the idea that this should be art, not something that's cartoony or amateur.
+
+To create museum or magazine quality work, use the design philosophy as the foundation. Create one single page, highly visual, design-forward PDF or PNG output (unless asked for more pages). Generally use repeating patterns and perfect shapes. Treat the abstract philosophical design as if it were a scientific bible, borrowing the visual language of systematic observation—dense accumulation of marks, repeated elements, or layered patterns that build meaning through patient repetition and reward sustained viewing. Add sparse, clinical typography and systematic reference markers that suggest this could be a diagram from an imaginary discipline, treating the invisible subject with the same reverence typically reserved for documenting observable phenomena. Anchor the piece with simple phrase(s) or details positioned subtly, using a limited color palette that feels intentional and cohesive. Embrace the paradox of using analytical visual language to express ideas about human experience: the result should feel like an artifact that proves something ephemeral can be studied, mapped, and understood through careful attention. This is true art.
+
+**Text as a contextual element**: Text is always minimal and visual-first, but let context guide whether that means whisper-quiet labels or bold typographic gestures. A punk venue poster might have larger, more aggressive type than a minimalist ceramics studio identity. Most of the time, font should be thin. All use of fonts must be design-forward and prioritize visual communication. Regardless of text scale, nothing falls off the page and nothing overlaps. Every element must be contained within the canvas boundaries with proper margins. Check carefully that all text, graphics, and visual elements have breathing room and clear separation. This is non-negotiable for professional execution. **IMPORTANT: Use different fonts if writing text. Search the `./canvas-fonts` directory. Regardless of approach, sophistication is non-negotiable.**
+
+Download and use whatever fonts are needed to make this a reality. Get creative by making the typography actually part of the art itself -- if the art is abstract, bring the font onto the canvas, not typeset digitally.
+
+To push boundaries, follow design instinct/intuition while using the philosophy as a guiding principle. Embrace ultimate design freedom and choice. Push aesthetics and design to the frontier.
+
+**CRITICAL**: To achieve human-crafted quality (not AI-generated), create work that looks like it took countless hours. Make it appear as though someone at the absolute top of their field labored over every detail with painstaking care. Ensure the composition, spacing, color choices, typography - everything screams expert-level craftsmanship. Double-check that nothing overlaps, formatting is flawless, every detail perfect. Create something that could be shown to people to prove expertise and rank as undeniably impressive.
+
+Output the final result as a single, downloadable .pdf or .png file, alongside the design philosophy used as a .md file.
+
+---
+
+## FINAL STEP
+
+**IMPORTANT**: The user ALREADY said "It isn't perfect enough. It must be pristine, a masterpiece if craftsmanship, as if it were about to be displayed in a museum."
+
+**CRITICAL**: To refine the work, avoid adding more graphics; instead refine what has been created and make it extremely crisp, respecting the design philosophy and the principles of minimalism entirely. Rather than adding a fun filter or refactoring a font, consider how to make the existing composition more cohesive with the art. If the instinct is to call a new function or draw a new shape, STOP and instead ask: "How can I make what's already here more of a piece of art?"
+
+Take a second pass. Go back to the code and refine/polish further to make this a philosophically designed masterpiece.
+
+## MULTI-PAGE OPTION
+
+To create additional pages when requested, create more creative pages along the same lines as the design philosophy but distinctly different as well. Bundle those pages in the same .pdf or many .pngs. Treat the first page as just a single page in a whole coffee table book waiting to be filled. Make the next pages unique twists and memories of the original. Have them almost tell a story in a very tasteful way. Exercise full creative freedom.

package/bundled-skills/citation-validator/SKILL.md

@@ -0,0 +1,203 @@
+---
+id: "citation-validator"
+title: "Citation Validator"
+category: "research"
+tags: ["citation validator", "role", "core responsibilities", "source quality rating system", "validation process", "output format", "citation validation report", "executive summary", "detailed findings", "recommendations"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/citation-validator"
+---
+
+---
+name: citation-validator
+description: 验证研究报告中所有声明的引用准确性、来源质量和格式规范性。确保每个事实性声明都有可验证的来源，并提供来源质量评级。当最终确定研究报告、审查他人研究、发布或分享研究之前使用此技能。
+---
+
+# Citation Validator
+
+## Role
+
+You are a **Citation Validator** responsible for ensuring research integrity by verifying that every factual claim in a research report has accurate, complete, and high-quality citations.
+
+## Core Responsibilities
+
+1. **Verify Citation Presence**: Every factual claim must have a citation
+2. **Validate Citation Completeness**: Each citation must have all required elements
+3. **Assess Source Quality**: Rate each source using the A-E quality scale
+4. **Check Citation Accuracy**: Verify citations actually support the claims
+5. **Detect Hallucinations**: Identify claims with no supporting sources
+6. **Format Consistency**: Ensure uniform citation format throughout
+
+## Citation Completeness Requirements
+
+### Every Citation Must Include:
+
+1. **Author/Organization** - Who created the content
+2. **Publication Date** - When it was published (YYYY format)
+3. **Source Title** - Name of the work
+4. **URL/DOI** - Direct link to verify
+5. **Page Numbers** (if applicable) - For PDFs and long documents
+
+### Acceptable Citation Formats:
+
+**Academic Papers**:
+
+```
+(Smith et al., 2023, p. 145)
+Full: Smith, J., Johnson, K., & Lee, M. (2023). "Title of Paper." Journal Name, 45(3), 140-156. https://doi.org/10.xxxx/xxxxx
+```
+
+**Industry Reports**:
+
+```
+(Gartner, 2024, "Cloud Computing Forecast")
+Full: Gartner. (2024). "Cloud Computing Market Forecast, 2024." Retrieved [date] from https://www.gartner.com/en/research/xxxxx
+```
+
+## Source Quality Rating System
+
+- **A - Excellent**: Peer-reviewed journals with impact factor, meta-analyses, RCTs, government regulatory bodies
+- **B - Good**: Cohort studies, clinical guidelines, reputable analysts (Gartner, Forrester), government websites
+- **C - Acceptable**: Expert opinion pieces, case reports, company white papers, reputable news outlets
+- **D - Weak**: Preprints, conference abstracts, blog posts without editorial oversight, crowdsourced content
+- **E - Very Poor**: Anonymous content, clear bias/conflict of interest, outdated sources, broken/suspicious links
+
+## Validation Process
+
+### Step 1: Claim Detection
+
+Scan the research content and identify all factual claims:
+
+- Statistics and numbers
+- Dates and timelines
+- Technical specifications
+- Market data (sizes, growth rates)
+- Performance claims
+- Quotes and paraphrases
+- Cause-effect statements
+
+### Step 2: Citation Presence Check
+
+For each factual claim, verify a citation exists.
+
+### Step 3: Citation Completeness Check
+
+Verify all required elements (author, date, title, URL/DOI, pages) are present.
+
+### Step 4: Source Quality Assessment
+
+Assign quality rating (A-E) to each complete citation.
+
+### Step 5: Citation Accuracy Verification
+
+Use WebSearch or WebFetch to find and verify the original source.
+
+### Step 6: Hallucination Detection
+
+**Red Flags**:
+
+1. No citation provided for factual claim
+2. Citation doesn't exist (URL leads nowhere)
+3. Citation exists but doesn't support claim
+4. Numbers suspiciously precise without source
+5. Generic source ("Industry reports") without specifics
+
+### Step 7: Chain-of-Verification for Critical Claims
+
+For high-stakes claims (medical, legal, financial):
+
+1. Find 2-3 independent sources supporting the claim
+2. Check for consensus among sources
+3. Identify any contradictions
+4. Assess source quality (prefer A-B ratings)
+5. Note uncertainty if sources disagree
+
+## Output Format
+
+```markdown
+# Citation Validation Report
+
+## Executive Summary
+
+- **Total Claims Analyzed**: [number]
+- **Claims with Citations**: [number] ([percentage]%)
+- **Complete Citations**: [number] ([percentage]%)
+- **Accurate Citations**: [number] ([percentage]%)
+- **Potential Hallucinations**: [number]
+- **Overall Quality Score**: [score]/10
+
+## Critical Issues (Immediate Action Required)
+
+[List any hallucinations or serious accuracy issues]
+
+## Detailed Findings
+
+[Line-by-line or claim-by-claim analysis]
+
+## Recommendations
+
+[Prioritized list of fixes]
+```
+
+## Tool Usage
+
+### WebSearch (for verification)
+
+Search for claims to verify: exact claim in quotes, keywords, author names, source titles
+
+### WebFetch (for source access)
+
+Access sources to confirm figures, dates, context, and find DOI/URL
+
+### Read/Write (for documentation)
+
+Save validation reports to `sources/citation_validation_report.md`
+
+## Special Considerations
+
+### Medical/Health Information
+
+- Require peer-reviewed sources (A-B ratings)
+- Verify PubMed IDs (PMID)
+- Distinguish between "proven" vs "preliminary"
+
+### Legal/Regulatory Information
+
+- Cite primary legal documents
+- Include docket numbers for regulations
+- Note jurisdictional scope
+
+### Market/Financial Data
+
+- Use primary sources (SEC filings, company reports)
+- Note reporting periods
+- Distinguish GAAP vs non-GAAP
+
+## Quality Score Calculation
+
+**Score Interpretation**:
+
+- **9-10**: Excellent - Professional research quality
+- **7-8**: Good - Acceptable for most purposes
+- **5-6**: Fair - Needs improvement
+- **3-4**: Poor - Significant issues
+- **0-2**: Very Poor - Not credible
+
+## Success Criteria
+
+- [ ] 100% of factual claims have citations
+- [ ] 100% of citations are complete
+- [ ] 95%+ of citations are accurate
+- [ ] No unexplained hallucinations
+- [ ] Average source quality ≥ B
+- [ ] Overall quality score ≥ 8/10
+
+## Examples
+
+See [examples.md](examples.md) for detailed usage examples.
+
+## Remember
+
+You are the **Citation Validator** - the last line of defense against misinformation and hallucinations. Your vigilance ensures research integrity and credibility.
+
+**Never compromise on citation quality. A well-sourced claim is worth infinitely more than an unsupported assertion.**

package/bundled-skills/clangd-lsp/SKILL.md

@@ -0,0 +1,52 @@
+---
+id: "clangd-lsp"
+title: "clangd-lsp"
+category: "other"
+tags: ["clangd-lsp", "supported extensions", "installation", "ubuntu/debian", "fedora", "arch linux", "more information"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/clangd-lsp"
+---
+
+# clangd-lsp
+
+C/C++ language server (clangd) for Claude Code, providing code intelligence, diagnostics, and formatting.
+
+## Supported Extensions
+
+`.c`, `.h`, `.cpp`, `.cc`, `.cxx`, `.hpp`, `.hxx`, `.C`, `.H`
+
+## Installation
+
+### Via Homebrew (macOS)
+
+```bash
+brew install llvm
+# Add to PATH: export PATH="/opt/homebrew/opt/llvm/bin:$PATH"
+```
+
+### Via package manager (Linux)
+
+```bash
+# Ubuntu/Debian
+sudo apt install clangd
+
+# Fedora
+sudo dnf install clang-tools-extra
+
+# Arch Linux
+sudo pacman -S clang
+```
+
+### Windows
+
+Download from [LLVM releases](https://github.com/llvm/llvm-project/releases) or install via:
+
+```bash
+winget install LLVM.LLVM
+```
+
+## More Information
+
+- [clangd Website](https://clangd.llvm.org/)
+- [Getting Started Guide](https://clangd.llvm.org/installation)

package/bundled-skills/code-review/SKILL.md

@@ -0,0 +1,280 @@
+---
+id: "code-review"
+title: "Code Review Plugin"
+category: "dev-tools"
+tags: ["code review plugin", "overview", "commands", "code review", "installation", "best practices", "workflow integration", "create pr with changes"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/code-review"
+---
+
+# Code Review Plugin
+
+Automated code review for pull requests using multiple specialized agents with confidence-based scoring to filter false positives.
+
+## Overview
+
+The Code Review Plugin automates pull request review by launching multiple agents in parallel to independently audit changes from different perspectives. It uses confidence scoring to filter out false positives, ensuring only high-quality, actionable feedback is posted.
+
+## Commands
+
+### `/code-review`
+
+Performs automated code review on a pull request using multiple specialized agents.
+
+**What it does:**
+
+1. Checks if review is needed (skips closed, draft, trivial, or already-reviewed PRs)
+2. Gathers relevant CLAUDE.md guideline files from the repository
+3. Summarizes the pull request changes
+4. Launches 4 parallel agents to independently review:
+   - **Agents #1 & #2**: Audit for CLAUDE.md compliance
+   - **Agent #3**: Scan for obvious bugs in changes
+   - **Agent #4**: Analyze git blame/history for context-based issues
+5. Scores each issue 0-100 for confidence level
+6. Filters out issues below 80 confidence threshold
+7. Posts review comment with high-confidence issues only
+
+**Usage:**
+
+```bash
+/code-review
+```
+
+**Example workflow:**
+
+```bash
+# On a PR branch, run:
+/code-review
+
+# Claude will:
+# - Launch 4 review agents in parallel
+# - Score each issue for confidence
+# - Post comment with issues ≥80 confidence
+# - Skip posting if no high-confidence issues found
+```
+
+**Features:**
+
+- Multiple independent agents for comprehensive review
+- Confidence-based scoring reduces false positives (threshold: 80)
+- CLAUDE.md compliance checking with explicit guideline verification
+- Bug detection focused on changes (not pre-existing issues)
+- Historical context analysis via git blame
+- Automatic skipping of closed, draft, or already-reviewed PRs
+- Links directly to code with full SHA and line ranges
+
+**Review comment format:**
+
+```markdown
+## Code review
+
+Found 3 issues:
+
+1. Missing error handling for OAuth callback (CLAUDE.md says "Always handle OAuth errors")
+
+https://github.com/owner/repo/blob/abc123.../src/auth.ts#L67-L72
+
+2. Memory leak: OAuth state not cleaned up (bug due to missing cleanup in finally block)
+
+https://github.com/owner/repo/blob/abc123.../src/auth.ts#L88-L95
+
+3. Inconsistent naming pattern (src/conventions/CLAUDE.md says "Use camelCase for functions")
+
+https://github.com/owner/repo/blob/abc123.../src/utils.ts#L23-L28
+```
+
+**Confidence scoring:**
+
+- **0**: Not confident, false positive
+- **25**: Somewhat confident, might be real
+- **50**: Moderately confident, real but minor
+- **75**: Highly confident, real and important
+- **100**: Absolutely certain, definitely real
+
+**False positives filtered:**
+
+- Pre-existing issues not introduced in PR
+- Code that looks like a bug but isn't
+- Pedantic nitpicks
+- Issues linters will catch
+- General quality issues (unless in CLAUDE.md)
+- Issues with lint ignore comments
+
+## Installation
+
+This plugin is included in the Claude Code repository. The command is automatically available when using Claude Code.
+
+## Best Practices
+
+### Using `/code-review`
+
+- Maintain clear CLAUDE.md files for better compliance checking
+- Trust the 80+ confidence threshold - false positives are filtered
+- Run on all non-trivial pull requests
+- Review agent findings as a starting point for human review
+- Update CLAUDE.md based on recurring review patterns
+
+### When to use
+
+- All pull requests with meaningful changes
+- PRs touching critical code paths
+- PRs from multiple contributors
+- PRs where guideline compliance matters
+
+### When not to use
+
+- Closed or draft PRs (automatically skipped anyway)
+- Trivial automated PRs (automatically skipped)
+- Urgent hotfixes requiring immediate merge
+- PRs already reviewed (automatically skipped)
+
+## Workflow Integration
+
+### Standard PR review workflow:
+
+```bash
+# Create PR with changes
+/code-review
+
+# Review the automated feedback
+# Make any necessary fixes
+# Merge when ready
+```
+
+### As part of CI/CD:
+
+```bash
+# Trigger on PR creation or update
+# Automatically posts review comments
+# Skip if review already exists
+```
+
+## Requirements
+
+- Git repository with GitHub integration
+- GitHub CLI (`gh`) installed and authenticated
+- CLAUDE.md files (optional but recommended for guideline checking)
+
+## Troubleshooting
+
+### Review takes too long
+
+**Issue**: Agents are slow on large PRs
+
+**Solution**:
+
+- Normal for large changes - agents run in parallel
+- 4 independent agents ensure thoroughness
+- Consider splitting large PRs into smaller ones
+
+### Too many false positives
+
+**Issue**: Review flags issues that aren't real
+
+**Solution**:
+
+- Default threshold is 80 (already filters most false positives)
+- Make CLAUDE.md more specific about what matters
+- Consider if the flagged issue is actually valid
+
+### No review comment posted
+
+**Issue**: `/code-review` runs but no comment appears
+
+**Solution**:
+Check if:
+
+- PR is closed (reviews skipped)
+- PR is draft (reviews skipped)
+- PR is trivial/automated (reviews skipped)
+- PR already has review (reviews skipped)
+- No issues scored ≥80 (no comment needed)
+
+### Link formatting broken
+
+**Issue**: Code links don't render correctly in GitHub
+
+**Solution**:
+Links must follow this exact format:
+
+```
+https://github.com/owner/repo/blob/[full-sha]/path/file.ext#L[start]-L[end]
+```
+
+- Must use full SHA (not abbreviated)
+- Must use `#L` notation
+- Must include line range with at least 1 line of context
+
+### GitHub CLI not working
+
+**Issue**: `gh` commands fail
+
+**Solution**:
+
+- Install GitHub CLI: `brew install gh` (macOS) or see [GitHub CLI installation](https://cli.github.com/)
+- Authenticate: `gh auth login`
+- Verify repository has GitHub remote
+
+## Tips
+
+- **Write specific CLAUDE.md files**: Clear guidelines = better reviews
+- **Include context in PRs**: Helps agents understand intent
+- **Use confidence scores**: Issues ≥80 are usually correct
+- **Iterate on guidelines**: Update CLAUDE.md based on patterns
+- **Review automatically**: Set up as part of PR workflow
+- **Trust the filtering**: Threshold prevents noise
+
+## Configuration
+
+### Adjusting confidence threshold
+
+The default threshold is 80. To adjust, modify the command file at `commands/code-review.md`:
+
+```markdown
+Filter out any issues with a score less than 80.
+```
+
+Change `80` to your preferred threshold (0-100).
+
+### Customizing review focus
+
+Edit `commands/code-review.md` to add or modify agent tasks:
+
+- Add security-focused agents
+- Add performance analysis agents
+- Add accessibility checking agents
+- Add documentation quality checks
+
+## Technical Details
+
+### Agent architecture
+
+- **2x CLAUDE.md compliance agents**: Redundancy for guideline checks
+- **1x bug detector**: Focused on obvious bugs in changes only
+- **1x history analyzer**: Context from git blame and history
+- **Nx confidence scorers**: One per issue for independent scoring
+
+### Scoring system
+
+- Each issue independently scored 0-100
+- Scoring considers evidence strength and verification
+- Threshold (default 80) filters low-confidence issues
+- For CLAUDE.md issues: verifies guideline explicitly mentions it
+
+### GitHub integration
+
+Uses `gh` CLI for:
+
+- Viewing PR details and diffs
+- Fetching repository data
+- Reading git blame and history
+- Posting review comments
+
+## Author
+
+Boris Cherny (boris@anthropic.com)
+
+## Version
+
+1.0.0