Skip to content

docs: update CLAUDE.md with riviere-extract-config dependencies - #87

Merged
NTCoding merged 1 commit into
mainfrom
issue-47-m4-d4-4-update-root-claude-md-
Jan 9, 2026
Merged

docs: update CLAUDE.md with riviere-extract-config dependencies#87
NTCoding merged 1 commit into
mainfrom
issue-47-m4-d4-4-update-root-claude-md-

Conversation

@NTCoding

@NTCoding NTCoding commented Jan 9, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Owner

User description

Closes #47

Summary

  • Document that riviere-extract-conventions depends on riviere-extract-config
  • Document that riviere-extract-ts depends on riviere-extract-config

Test plan

  • Changes are documentation only
  • Package dependency structure is accurately reflected in CLAUDE.md

🤖 Generated with Claude Code

PR Type

Documentation

Description

  • Document riviere-extract-config dependencies in package list

  • Clarify that two packages depend on riviere-extract-config

Diagram Walkthrough

flowchart LR
  A["riviere-extract-config"] -- "dependency" --> B["riviere-extract-conventions"]
  A -- "dependency" --> C["riviere-extract-ts"]
Loading

File Walkthrough
Relevant files
Documentation
CLAUDE.md
Add riviere-extract-config dependencies to package list   

CLAUDE.md

  • Added dependency notation to riviere-extract-conventions package
    description
  • Added dependency notation to riviere-extract-ts package description
  • Clarified package dependency structure in documentation
 +2/-2     

Summary by CodeRabbit

  • Documentation
    • Updated package dependency documentation to reflect configuration requirements for extraction packages.

✏️ Tip: You can customize this high-level summary in your review settings.

@NTCoding @claude
docs: add riviere-extract-config dependencies to CLAUDE.md
960a36d 
Update package list to document that riviere-extract-conventions
and riviere-extract-ts both depend on riviere-extract-config.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@coderabbitai

coderabbitai Bot commented Jan 9, 2026 •
edited
Loading

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The CLAUDE.md file was updated to document package dependency relationships. Two extraction packages—riviere-extract-conventions and riviere-extract-ts—now explicitly indicate their dependence on riviere-extract-config, clarifying the package structure for developers and AI assistants.

Changes

Cohort / File(s) Change Summary
Documentation Updates
CLAUDE.md		 Added dependency annotations to two package entries, noting that @living-architecture/riviere-extract-conventions and @living-architecture/riviere-extract-ts both depend on riviere-extract-config

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested labels

Review effort 1/5

Poem

🐰 In CLAUDE's pages, where packages play,
Dependencies now clearly display,
Extract-conventions and extract-ts aligned,
With config as their base, carefully designed! 📚✨

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ade6b5c and 960a36d.

📒 Files selected for processing (1)
  • CLAUDE.md

Comment @coderabbitai help to get the list of available commands and usage tips.

@qodo-code-review

qodo-code-review Bot commented Jan 9, 2026

Copy link
Copy Markdown
Contributor

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢
No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🟡
🎫 #47
🟢 Update CLAUDE.md to list the three new extraction packages:
@living-architecture/riviere-extract-config,
@living-architecture/riviere-extract-conventions, and
@living-architecture/riviere-extract-ts.
Make the extraction package dependency relationships clear in `CLAUDE.md`.
⚪ Ensure each listed extraction package description accurately reflects the actual package
purpose.
Codebase Duplication Compliance
⚪
Codebase context is not defined

Follow the guide to enable codebase context checks.

Custom Compliance
🟢
Generic: Comprehensive Audit Trails

Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Meaningful Naming and Self-Documenting Code

Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Robust Error Handling and Edge Case Management

Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Error Handling

Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Logging Practices

Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Security-First Input Validation and Data Handling

Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules
Compliance status legend 🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

@qodo-code-review

qodo-code-review Bot commented Jan 9, 2026

Copy link
Copy Markdown
Contributor

PR Code Suggestions ✨

Explore these optional code suggestions:

CategorySuggestion                                                                                                                                    Impact
General
Wrap dependency package names in backticks

For consistency and clarity, wrap the dependency package name in backticks and
use its full scoped name.

CLAUDE.md [20-21]

-- `@living-architecture/riviere-extract-conventions` - Decorators for marking architectural components (depends on riviere-extract-config)
-- `@living-architecture/riviere-extract-ts` - TypeScript component extractor using ts-morph for AST parsing (depends on riviere-extract-config)
+- `@living-architecture/riviere-extract-conventions` - Decorators for marking architectural components (depends on `@living-architecture/riviere-extract-config`)
+- `@living-architecture/riviere-extract-ts` - TypeScript component extractor using ts-morph for AST parsing (depends on `@living-architecture/riviere-extract-config`)
  • Apply / Chat
Suggestion importance[1-10]: 4

__

Why: The suggestion correctly identifies an inconsistency in the documentation and proposes a change that improves clarity and follows the existing format of using full, backticked package names.

Low
  • More

@NTCoding
NTCoding merged commit d749d63 into main Jan 9, 2026
13 of 14 checks passed
@sonarqubecloud

sonarqubecloud Bot commented Jan 9, 2026

Copy link
Copy Markdown

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Review effort 1/5

Projects

None yet

Milestone

No milestone

Development

See More

Successfully merging this pull request may close these issues.

[M4-D4.4] Update root CLAUDE.md with new packages

1 participant

@NTCoding