chore(release): prepare core cli 0.46.28

[djm81]

Summary

• Sync the latest main fix back into the dev release-prep path.
• Bump the core CLI package version from 0.46.27 to 0.46.28 across all canonical version files.
• Update CHANGELOG.md for the release and implement [Docs] Add AI bloat simplify callout after modules rollout #573 with core README/docs callouts for ai_bloat advisories and /specfact.08-simplify.

Validation

• python scripts/check_version_sources.py
• python scripts/check_doc_frontmatter.py
• python scripts/check-docs-commands.py
• python scripts/check-cross-site-links.py --warn-only (rerun escalated; 25 modules.specfact.io URLs checked)
• hatch run check-pypi-ahead (0.46.28 ahead of PyPI latest 0.46.25)
• bash scripts/pre-commit-quality-checks.sh all
• commit hook full pre-commit suite, including SpecFact code review gate: 0 findings; contract tests skipped by contract-test-status because no input changes

Closes #573.

[strix-security]

Strix is installed on this repository, but we could not run this PR security review because this workspace does not have an active plan. If you'd like to continue receiving code reviews, you can add a payment method or manage billing here.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e3b985fc-d797-44ce-831d-100bcbf02d33

📥 Commits

Reviewing files that changed from the base of the PR and between a6ae72d and 9086e1e.

📒 Files selected for processing (9)

• CHANGELOG.md
• README.md
• docs/getting-started/quickstart.md
• docs/index.md
• docs/modules/code-review.md
• pyproject.toml
• setup.py
• src/__init__.py
• src/specfact_cli/__init__.py

✅ Files skipped from review due to trivial changes (7)

• README.md
• CHANGELOG.md
• src/init.py
• docs/modules/code-review.md
• docs/index.md
• docs/getting-started/quickstart.md
• setup.py

📜 Recent review details

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: Linting (ruff, pylint, safe-write guard)
• GitHub Check: Contract-First CI
• GitHub Check: Compatibility (Python 3.11)
• GitHub Check: Tests (Python 3.12)
• GitHub Check: Type Checking (basedpyright)

🧰 Additional context used

📓 Path-based instructions (8)

{src/__init__.py,pyproject.toml,setup.py}

📄 CodeRabbit inference engine (.cursor/rules/python-github-rules.mdc)

{src/__init__.py,pyproject.toml,setup.py}: Update src/init.py first as primary source of truth for package version, then pyproject.toml and setup.py
Maintain version synchronization across src/init.py, pyproject.toml, and setup.py

Files:

• pyproject.toml

{pyproject.toml,setup.py,src/__init__.py}

📄 CodeRabbit inference engine (.cursor/rules/testing-and-build-guide.mdc)

Manually update version numbers in pyproject.toml, setup.py, and src/init.py when making a formal version change

Files:

• pyproject.toml

pyproject.toml

📄 CodeRabbit inference engine (.cursorrules)

When updating the version in pyproject.toml, ensure it's newer than the latest PyPI version. The CI/CD pipeline will automatically publish to PyPI only if the new version is greater than the published version

Files:

• pyproject.toml

**/*.py

📄 CodeRabbit inference engine (.cursor/rules/python-github-rules.mdc)

**/*.py: Maintain minimum 80% test coverage, with 100% coverage for critical paths in Python code
Use clear naming and self-documenting code, preferring clear names over comments
Ensure each function/class has a single clear purpose (Single Responsibility Principle)
Extract common patterns to avoid code duplication (DRY principle)
Apply SOLID object-oriented design principles in Python code
Use type hints everywhere in Python code and enable basedpyright strict mode
Use Pydantic models for data validation and serialization in Python
Use async/await for I/O operations in Python code
Use context managers for resource management in Python
Use dataclasses for simple data containers in Python
Enforce maximum line length of 120 characters in Python code
Use 4 spaces for indentation in Python code (no tabs)
Use 2 blank lines between classes and 1 blank line between methods in Python
Organize imports in order: Standard library → Third party → Local in Python files
Use snake_case for variables and functions in Python
Use PascalCase for class names in Python
Use UPPER_SNAKE_CASE for constants in Python
Use leading underscore (_) for private methods in Python classes
Use snake_case for Python file names
Enable basedpyright strict mode with strict type checking configuration in Python
Use Google-style docstrings for functions and classes in Python
Include comprehensive exception handling with specific exception types in Python code
Use logging with structured context (extra parameters) instead of print statements
Use retry logic with tenacity decorators (@retry) for operations that might fail
Use Pydantic BaseSettings for environment-based configuration in Python
Validate user input using Pydantic validators in Python models
Use @lru_cache and Redis-based caching for expensive calculations in Python
Run code formatting with Black (120 character line length) and isort in Python
Run type checking with basedpyright on all Python files
Run linting with ruff and pylint on all Pyth...

Files:

• src/specfact_cli/__init__.py

src/**/*.py

📄 CodeRabbit inference engine (.cursor/rules/spec-fact-cli-rules.mdc)

src/**/*.py: All code changes must be followed by running the full test suite using the smart test system.
All Python files in src/ and tools/ directories must have corresponding test files in tests/ directory. If you modify src/common/logger_setup.py, you MUST have tests/unit/common/test_logger_setup.py. NO EXCEPTIONS - even small changes require tests.
All new Python runtime code files must have corresponding test files created BEFORE committing the code. NO EXCEPTIONS - no code without tests.
Test Coverage Validation: Run hatch run smart-test-unit for modified files, hatch run smart-test-folder for modified directories, and hatch run smart-test-full before committing. ALL TESTS MUST PASS.
All components must support TEST_MODE=true environment variable with test-specific behavior defined as: if os.environ.get('TEST_MODE') == 'true': # test-specific behavior
Use src/common/logger_setup.py for all logging via: from common.logger_setup import get_logger; logger = get_logger(name)
Use src/common/redis_client.py with fallback for Redis operations via: from common.redis_client import get_redis_client; redis_client = get_redis_client()
Type checking must pass with no errors using: mypy .
Test coverage must meet or exceed 80% total coverage. New code must have corresponding tests. Modified code must maintain or improve coverage. Critical paths must have 100% coverage.
Use Pydantic v2 validation for all context and data schemas.

Add/update contracts on new or modified public APIs, stateful classes and adapters using icontract decorators and beartype runtime type checks

src/**/*.py: Meaningful Naming — identifiers reveal intent; avoid abbreviations. Identifiers in src/ must use snake_case (modules/functions), PascalCase (classes), UPPER_SNAKE_CASE (constants). Avoid single-letter names outside short loop variables.
KISS — keep functions and modules small and single-purpose. Maximum function length: 120 lines (Phase A error threshold). Maximum cyclomati...

Files:

• src/specfact_cli/__init__.py

@(src|tests)/**/*.py

📄 CodeRabbit inference engine (.cursor/rules/spec-fact-cli-rules.mdc)

Linting must pass with no errors using: pylint src tests

Files:

• src/specfact_cli/__init__.py

**/*.{py,pyi}

📄 CodeRabbit inference engine (.cursorrules)

**/*.{py,pyi}: After any code changes, follow these steps in order: (1) Apply linting and formatting to ensure code quality: hatch run format, (2) Type checking: hatch run type-check (basedpyright), (3) Contract-first approach: Run hatch run contract-test for contract validation, (4) Run full test suite: hatch test --cover -v, (5) Verify all tests pass and contracts are satisfied, (6) Fix any issues and repeat steps until all tests pass
All public APIs must have @icontract decorators and @beartype type checking
Use Pydantic models for all data structures with data validation
Only write high-value comments if at all. Avoid talking to the user through comments

Files:

• src/specfact_cli/__init__.py

src/specfact_cli/**/*.py

⚙️ CodeRabbit configuration file

src/specfact_cli/**/*.py: Focus on modular CLI architecture: lazy module loading, registry/bootstrap patterns, and
dependency direction. Flag breaking changes to public APIs, Pydantic models, and resource
bundling. Verify @icontract + @beartype on public surfaces; prefer centralized logging
(get_bridge_logger) over print().

Files:

• src/specfact_cli/__init__.py

🔀 Multi-repo context nold-ai/specfact-cli-modules

Linked repositories findings

nold-ai/specfact-cli-modules

• New/recognized ReviewFinding category "ai_bloat" implemented and exercised in multiple places:
  • Tests asserting category and score-neutral behavior: [::nold-ai/specfact-cli-modules::tests/unit/specfact_code_review/run/test_scorer.py:22-72] (score-neutral, severity=info).
  • Review schema and spec require accept-list update: [::nold-ai/specfact-cli-modules::openspec/changes/code-review-ai-bloat-detection/specs/code-review-ai-bloat-detection/spec.md:5-31].
• Semgrep rules mapped to category and treated as info:
  • SEMGREP_RULE_CATEGORY mappings and allowed literal include "ai_bloat": [::nold-ai/specfact-cli-modules::packages/specfact-code-review/src/specfact_code_review/tools/semgrep_runner.py:27-31][::nold-ai/specfact-cli-modules::packages/specfact-code-review/src/specfact_code_review/tools/semgrep_runner.py:37].
  • Semgrep rules file: [::nold-ai/specfact-cli-modules::packages/specfact-code-review/resources/semgrep-rules/ai-bloat.yaml].
• AST-based ai_bloat runner added and wired:
  • ai_bloat_runner implementation and exports: [::nold-ai/specfact-cli-modules::packages/specfact-code-review/src/specfact_code_review/tools/ai_bloat_runner.py:94-254] and [::nold-ai/specfact-cli-modules::packages/specfact-code-review/src/specfact_code_review/tools/init.py:3,15].
  • Runner wired into orchestration: [::nold-ai/specfact-cli-modules::packages/specfact-code-review/src/specfact_code_review/run/runner.py:24,256].
• Policy pack registering ai_bloat principle and advisory mode:
  • ai-bloat policy pack entries: [::nold-ai/specfact-cli-modules::packages/specfact-code-review/resources/policy-packs/specfact/ai-bloat-patterns.yaml].
• Pre-commit hook behavior updated to preserve ai_bloat JSON and not block commits when only ai_bloat/info present:
  • Hook counting and summary logic: [::nold-ai/specfact-cli-modules::scripts/pre_commit_code_review.py:224-281].
  • Tests covering hook semantics: [::nold-ai/specfact-cli-modules::tests/unit/scripts/test_pre_commit_code_review.py:150-216].
• Project prompt for human-confirmed simplification exists and reads .specfact/code-review.json filtering category==ai_bloat:
  • Prompt resource: [::nold-ai/specfact-cli-modules::packages/specfact-project/resources/prompts/specfact.08-simplify.md:21-61].
  • Docs/quickstart reference using prompt: [::nold-ai/specfact-cli-modules::docs/quickstart-ai-bloat.md:29-89], [::nold-ai/specfact-cli-modules::README.md:7].
• Scoring and runner behaviors explicitly ignore/handle ai_bloat as score-neutral and info-only:
  • Scorer skip for ai_bloat: [::nold-ai/specfact-cli-modules::packages/specfact-code-review/src/specfact_code_review/run/scorer.py:53].
  • Findings allow-list includes ai_bloat: [::nold-ai/specfact-cli-modules::packages/specfact-code-review/src/specfact_code_review/run/findings.py:27,85].

Impact for the core specfact-cli PR under review:

• Core consumers that parse ReviewFinding.category must accept the new literal "ai_bloat" and handle info/advisory findings without treating them as blocking or score-impacting. The modules repo demonstrates the required changes (schema allow-list, scorer logic, pre-commit behavior, prompt workflow). Verify core's ReviewFinding schema/parsers and any score/blocking logic follow the same additive, non-blocking contract.

🔇 Additional comments (2)

pyproject.toml (1)

7-7: LGTM!

src/specfact_cli/__init__.py (1)

48-48: LGTM!

---

📝 Walkthrough

Version Bump & Release Artifacts

• Core CLI version: 0.46.27 → 0.46.28 (patch release)
• Version files updated: pyproject.toml, setup.py, src/init.py, src/specfact_cli/init.py
• CHANGELOG.md: added 0.46.28 (2026-05-21) entry documenting ai_bloat guidance refinement and sync of a main-branch fix back into dev

User-Visible Behavior and CLI Surface

• Code Review: documents that the Code Review bundle can emit ai_bloat advisory findings for AI-amplified code patterns.
• Behavior/Guidance:
  • ai_bloat findings are advisory-only, score-neutral, and are not an AI-authorship classifier.
  • Users are directed to review the generated report at .specfact/code-review.json.
  • Recommended workflow: use the IDE prompt /specfact.08-simplify to inspect and confirm proposed simplifications (human confirmation required).
• Docs touched:
  • README.md: note describing Code Review ai_bloat advisories and link to quickstart and project IDE workflow.
  • docs/index.md: updated last_reviewed and added "New in Code Review" callout describing ai_bloat.
  • docs/getting-started/quickstart.md: clarified ai_bloat severity (info), advisory nature, JSON report generation, and simplification workflow.
  • docs/modules/code-review.md: expanded module guidance for advisory cleanup, reporting, and IDE-driven simplifications.

Contract/API Impact

• No breaking changes to CLI commands, options, or defaults.
• No changes to public functions, Pydantic models, or package/module APIs.
• Package init behavior unchanged aside from version export; module boundaries remain stable.

Testing and Quality Gates

• Validation performed:
  • python scripts/check_version_sources.py
  • python scripts/check_doc_frontmatter.py
  • python scripts/check-docs-commands.py
  • python scripts/check-cross-site-links.py --warn-only (checked 25 modules.specfact.io URLs)
  • hatch run check-pypi-ahead (confirms 0.46.28 ahead of PyPI 0.46.25)
  • bash scripts/pre-commit-quality-checks.sh (all)
  • commit hook full pre-commit suite (SpecFact code review gate): 0 findings; contract tests skipped via contract-test-status (no input changes)
• Testing/coverage impact: none (docs- and metadata-only changes)

Related Issues, Scope, and Notes

• Closes issue #573 — adds core README/docs callout and points to modules Code Review bundle capability.
• Purpose: sync main fix into dev and prepare a patch release.
• Scope: documentation, release metadata, and docs frontmatter updates; follows up on modules changes (specfact-cli-modules#269 / openspec change for code-review-ai-bloat-detection).

Walkthrough

Version 0.46.28 patch release updates the package version across metadata files and changelog, then documents the new ai_bloat advisory feature in README, homepage, quickstart, and module docs—clarifying findings are advisory, score-neutral, and reviewable via the /specfact.08-simplify IDE prompt with JSON output.

Changes

Release 0.46.28 and AI bloat guidance

Layer / File(s)	Summary
Version metadata and changelog for 0.46.28 CHANGELOG.md, pyproject.toml, setup.py, src/__init__.py, src/specfact_cli/__init__.py	Release version incremented from 0.46.27 to 0.46.28 across package version declarations and documented in CHANGELOG with entries for Code Review AI bloat guidance and a core CLI metadata patch-bump.
AI bloat advisory documentation README.md, docs/index.md, docs/getting-started/quickstart.md, docs/modules/code-review.md	Added and updated docs to introduce ai_bloat advisory findings (severity info, score-neutral, not an authorship classifier), where the JSON report is written (.specfact/code-review.json), and the /specfact.08-simplify IDE prompt + quickstart workflow to review/apply simplifications.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• nold-ai/specfact-cli#455: Both PRs update the same version-export points (__version__ in src/specfact_cli/__init__.py and package version in pyproject.toml/setup.py) plus changelog entries for a patch release.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title 'chore(release): prepare core cli 0.46.28' follows Conventional Commits style with a 'chore' prefix and clearly describes the release preparation objective.
Description check	✅ Passed	The PR description provides a clear summary of changes, validation steps performed, and references the resolved issue #573, though it doesn't follow the full repository template structure.
Linked Issues check	✅ Passed	The PR fulfills all coding requirements from issue #573: README/docs callouts added for ai_bloat advisories, /specfact.08-simplify IDE prompt referenced, findings marked as advisory/score-neutral/human-confirmed, and quickstart documentation updated with AI bloat guidance.
Out of Scope Changes check	✅ Passed	All changes are directly scoped to release preparation (#573 implementation): version bumps, CHANGELOG, README, quickstart docs, and module docs—no extraneous code or API alterations.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-core-cli-patch

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/modules/code-review.md`:
- Around line 40-44: The docs state `severity=info` and “score-neutral” but
later the scoring section assigns `info: -1`, which conflicts for the `ai_bloat`
rule; update the description around `ai_bloat` (the block that currently lists
`severity=info`, `advisory-only`, `score-neutral`, and the note about
`.specfact/code-review.json`) to explicitly state that `ai_bloat` is
advisory-only and exempt from the `info` severity deduction (i.e., remains
score-neutral even though it has severity=info), so readers understand that
`ai_bloat` will not apply the `info: -1` penalty and that reports are written to
`.specfact/code-review.json` when all severities are included.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 12dde960-aaff-4e1b-ba0b-cc4b6e05caa5

📥 Commits

Reviewing files that changed from the base of the PR and between b58f924 and a6ae72d.

📒 Files selected for processing (9)

• CHANGELOG.md
• README.md
• docs/getting-started/quickstart.md
• docs/index.md
• docs/modules/code-review.md
• pyproject.toml
• setup.py
• src/__init__.py
• src/specfact_cli/__init__.py

📜 Review details

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Tests (Python 3.12)

🧰 Additional context used

📓 Path-based instructions (13)

**/*.py

📄 CodeRabbit inference engine (.cursor/rules/python-github-rules.mdc)

**/*.py: Maintain minimum 80% test coverage, with 100% coverage for critical paths in Python code
Use clear naming and self-documenting code, preferring clear names over comments
Ensure each function/class has a single clear purpose (Single Responsibility Principle)
Extract common patterns to avoid code duplication (DRY principle)
Apply SOLID object-oriented design principles in Python code
Use type hints everywhere in Python code and enable basedpyright strict mode
Use Pydantic models for data validation and serialization in Python
Use async/await for I/O operations in Python code
Use context managers for resource management in Python
Use dataclasses for simple data containers in Python
Enforce maximum line length of 120 characters in Python code
Use 4 spaces for indentation in Python code (no tabs)
Use 2 blank lines between classes and 1 blank line between methods in Python
Organize imports in order: Standard library → Third party → Local in Python files
Use snake_case for variables and functions in Python
Use PascalCase for class names in Python
Use UPPER_SNAKE_CASE for constants in Python
Use leading underscore (_) for private methods in Python classes
Use snake_case for Python file names
Enable basedpyright strict mode with strict type checking configuration in Python
Use Google-style docstrings for functions and classes in Python
Include comprehensive exception handling with specific exception types in Python code
Use logging with structured context (extra parameters) instead of print statements
Use retry logic with tenacity decorators (@retry) for operations that might fail
Use Pydantic BaseSettings for environment-based configuration in Python
Validate user input using Pydantic validators in Python models
Use @lru_cache and Redis-based caching for expensive calculations in Python
Run code formatting with Black (120 character line length) and isort in Python
Run type checking with basedpyright on all Python files
Run linting with ruff and pylint on all Pyth...

Files:

• setup.py
• src/specfact_cli/__init__.py
• src/__init__.py

{src/__init__.py,pyproject.toml,setup.py}

📄 CodeRabbit inference engine (.cursor/rules/python-github-rules.mdc)

{src/__init__.py,pyproject.toml,setup.py}: Update src/init.py first as primary source of truth for package version, then pyproject.toml and setup.py
Maintain version synchronization across src/init.py, pyproject.toml, and setup.py

Files:

• setup.py
• pyproject.toml
• src/__init__.py

{pyproject.toml,setup.py,src/__init__.py}

📄 CodeRabbit inference engine (.cursor/rules/testing-and-build-guide.mdc)

Manually update version numbers in pyproject.toml, setup.py, and src/init.py when making a formal version change

Files:

• setup.py
• pyproject.toml
• src/__init__.py

**/*.{py,pyi}

📄 CodeRabbit inference engine (.cursorrules)

**/*.{py,pyi}: After any code changes, follow these steps in order: (1) Apply linting and formatting to ensure code quality: hatch run format, (2) Type checking: hatch run type-check (basedpyright), (3) Contract-first approach: Run hatch run contract-test for contract validation, (4) Run full test suite: hatch test --cover -v, (5) Verify all tests pass and contracts are satisfied, (6) Fix any issues and repeat steps until all tests pass
All public APIs must have @icontract decorators and @beartype type checking
Use Pydantic models for all data structures with data validation
Only write high-value comments if at all. Avoid talking to the user through comments

Files:

• setup.py
• src/specfact_cli/__init__.py
• src/__init__.py

src/**/*.py

📄 CodeRabbit inference engine (.cursor/rules/spec-fact-cli-rules.mdc)

src/**/*.py: All code changes must be followed by running the full test suite using the smart test system.
All Python files in src/ and tools/ directories must have corresponding test files in tests/ directory. If you modify src/common/logger_setup.py, you MUST have tests/unit/common/test_logger_setup.py. NO EXCEPTIONS - even small changes require tests.
All new Python runtime code files must have corresponding test files created BEFORE committing the code. NO EXCEPTIONS - no code without tests.
Test Coverage Validation: Run hatch run smart-test-unit for modified files, hatch run smart-test-folder for modified directories, and hatch run smart-test-full before committing. ALL TESTS MUST PASS.
All components must support TEST_MODE=true environment variable with test-specific behavior defined as: if os.environ.get('TEST_MODE') == 'true': # test-specific behavior
Use src/common/logger_setup.py for all logging via: from common.logger_setup import get_logger; logger = get_logger(name)
Use src/common/redis_client.py with fallback for Redis operations via: from common.redis_client import get_redis_client; redis_client = get_redis_client()
Type checking must pass with no errors using: mypy .
Test coverage must meet or exceed 80% total coverage. New code must have corresponding tests. Modified code must maintain or improve coverage. Critical paths must have 100% coverage.
Use Pydantic v2 validation for all context and data schemas.

Add/update contracts on new or modified public APIs, stateful classes and adapters using icontract decorators and beartype runtime type checks

src/**/*.py: Meaningful Naming — identifiers reveal intent; avoid abbreviations. Identifiers in src/ must use snake_case (modules/functions), PascalCase (classes), UPPER_SNAKE_CASE (constants). Avoid single-letter names outside short loop variables.
KISS — keep functions and modules small and single-purpose. Maximum function length: 120 lines (Phase A error threshold). Maximum cyclomati...

Files:

• src/specfact_cli/__init__.py
• src/__init__.py

@(src|tests)/**/*.py

📄 CodeRabbit inference engine (.cursor/rules/spec-fact-cli-rules.mdc)

Linting must pass with no errors using: pylint src tests

Files:

• src/specfact_cli/__init__.py
• src/__init__.py

src/specfact_cli/**/*.py

⚙️ CodeRabbit configuration file

src/specfact_cli/**/*.py: Focus on modular CLI architecture: lazy module loading, registry/bootstrap patterns, and
dependency direction. Flag breaking changes to public APIs, Pydantic models, and resource
bundling. Verify @icontract + @beartype on public surfaces; prefer centralized logging
(get_bridge_logger) over print().

Files:

• src/specfact_cli/__init__.py

**/*.{md,mdc}

📄 CodeRabbit inference engine (.cursor/rules/markdown-rules.mdc)

**/*.{md,mdc}: Do not use more than one consecutive blank line anywhere in the document (MD012: No Multiple Consecutive Blank Lines)
Fenced code blocks should be surrounded by blank lines (MD031: Fenced Code Blocks)
Lists should be surrounded by blank lines (MD032: Lists)
Files must end with a single empty line (MD047: Files Must End With Single Newline)
Lines should not have trailing spaces (MD009: No Trailing Spaces)
Use asterisks (**) for strong emphasis, not underscores (__) (MD050: Strong Style)
Fenced code blocks must have a language specified (MD040: Fenced Code Language)
Headers should increment by one level at a time (MD001: Header Increment)
Headers should be surrounded by blank lines (MD022: Headers Should Be Surrounded By Blank Lines)
Only one top-level header (H1) is allowed per document (MD025: Single H1 Header)
Use consistent list markers, preferring dashes (-) for unordered lists (MD004: List Style)
Nested unordered list items should be indented consistently, typically by 2 spaces (MD007: Unordered List Indentation)
Use exactly one space after the list marker (e.g., -, *, +, 1.) (MD030: Spaces After List Markers)
Use incrementing numbers for ordered lists (MD029: Ordered List Item Prefix)
Enclose bare URLs in angle brackets or format them as links (MD034: Bare URLs)
Don't use spaces immediately inside code spans (MD038: Spaces Inside Code Spans)
Use consistent indentation (usually 2 or 4 spaces) throughout markdown files
Keep line length under 120 characters in markdown files
Use reference-style links for better readability in markdown files
Use a trailing slash for directory paths in markdown files
Ensure proper escaping of special characters in markdown files

Files:

• docs/index.md
• docs/getting-started/quickstart.md
• CHANGELOG.md
• README.md
• docs/modules/code-review.md

docs/**/*.md

📄 CodeRabbit inference engine (.cursor/rules/spec-fact-cli-rules.mdc)

Update architecture documentation in docs/ for architecture changes, state machine documentation for FSM modifications, interface documentation for API changes, and configuration guides for configuration changes. DO NOT create internal docs in specfact-cli repo folder that should not be visible to end users; use the respective internal repository instead.

Files:

• docs/index.md
• docs/getting-started/quickstart.md
• docs/modules/code-review.md

---

⚙️ CodeRabbit configuration file

docs/**/*.md: User-facing accuracy: CLI examples match current behavior; preserve Jekyll front matter;
call out when README/docs index need sync.

Files:

• docs/index.md
• docs/getting-started/quickstart.md
• docs/modules/code-review.md

**/*.md

📄 CodeRabbit inference engine (.cursorrules)

Avoid markdown linting errors (refer to markdown-rules)

Files:

• docs/index.md
• docs/getting-started/quickstart.md
• CHANGELOG.md
• README.md
• docs/modules/code-review.md

CHANGELOG.md

📄 CodeRabbit inference engine (.cursor/rules/python-github-rules.mdc)

Include new version entries at the top of CHANGELOG.md when updating versions

Update CHANGELOG.md with all code changes as part of version control requirements.

Update CHANGELOG.md to document all significant changes under Added, Fixed, Changed, or Removed sections when making a version change

Files:

• CHANGELOG.md

pyproject.toml

📄 CodeRabbit inference engine (.cursorrules)

When updating the version in pyproject.toml, ensure it's newer than the latest PyPI version. The CI/CD pipeline will automatically publish to PyPI only if the new version is greater than the published version

Files:

• pyproject.toml

@(README.md|AGENTS.md)

📄 CodeRabbit inference engine (.cursor/rules/spec-fact-cli-rules.mdc)

Check README.md and AGENTS.md for current project status and development guidelines. Review .cursor/rules/ for detailed development standards and testing procedures.

Files:

• README.md

🔀 Multi-repo context nold-ai/specfact-cli-modules

nold-ai/specfact-cli-modules — relevant cross-repo findings

• New/adopted review category "ai_bloat" appears across code, rules, docs, and tests:

  • tests asserting ai_bloat category and scorer behaviour: tests/unit/specfact_code_review/run/test_scorer.py (score-neutral) and many run/runner tests referencing "ai_bloat". [::nold-ai/specfact-cli-modules::tests/unit/specfact_code_review/run/test_scorer.py]
  • semgrep/AST rule resources and policy pack referenced: packages/specfact-code-review/resources/semgrep-rules/ai-bloat.yaml and packages/specfact-code-review/resources/policy-packs/specfact/ai-bloat-patterns.yaml (referenced in resource payload tests). [::nold-ai/specfact-cli-modules::packages/specfact-code-review/resources/semgrep-rules/ai-bloat.yaml][::nold-ai/specfact-cli-modules::packages/specfact-code-review/resources/policy-packs/specfact/ai-bloat-patterns.yaml]
  • Tests ensuring resource payloads include ai-bloat files: tests/unit/test_bundle_resource_payloads.py lines asserting ai-bloat filenames. [::nold-ai/specfact-cli-modules::tests/unit/test_bundle_resource_payloads.py]

• Runner wiring and schema expectations:

  • Design/spec describes adding "ai_bloat" to ReviewFinding.category and emitting severity=info (advisory, score-neutral): openspec/changes/code-review-ai-bloat-detection/design.md and specs files. [::nold-ai/specfact-cli-modules::openspec/changes/code-review-ai-bloat-detection/design.md][::nold-ai/specfact-cli-modules::openspec/changes/code-review-ai-bloat-detection/specs/code-review-ai-bloat-detection/spec.md]
  • Semgrep runner mapping update required: SEMGREP_RULE_CATEGORY referenced in design/tasks and code. Tests mention mapping in packages/.../semgrep_runner.py. [::nold-ai/specfact-cli-modules::openspec/changes/code-review-ai-bloat-detection/tasks.md][::nold-ai/specfact-cli-modules::tests/unit/specfact_code_review/tools/test_semgrep_runner.py]

• Pre-commit / CLI behaviour updated to surface ai_bloat in JSON but not block commits:

  • scripts/pre_commit_code_review.py: writes .specfact/code-review.json and counts ai_bloat, ensures hook exits zero when only ai_bloat/info findings present and prints stderr summary. Tests cover these behaviours. [::nold-ai/specfact-cli-modules::scripts/pre_commit_code_review.py][::nold-ai/specfact-cli-modules::tests/unit/scripts/test_pre_commit_code_review.py]

• IDE prompt for simplifying ai_bloat findings:

  • Prompt resource present: packages/specfact-project/resources/prompts/specfact.08-simplify.md describing reading .specfact/code-review.json, filtering category == "ai_bloat", and driving accept/reject edits via IDE slash command /specfact.08-simplify. [::nold-ai/specfact-cli-modules::packages/specfact-project/resources/prompts/specfact.08-simplify.md]

• Docs and quickstart additions:

  • Multiple docs updated/added to explain ai_bloat advisory framing and workflows, including docs pages and quickstart instructions referenced in openspec change tasks and docs paths. [::nold-ai/specfact-cli-modules::openspec/changes/code-review-ai-bloat-detection/tasks.md][::nold-ai/specfact-cli-modules::docs]

Implication for this PR (specfact-cli core):

• Core should not break: modules introduce a new review category ("ai_bloat") and a project prompt (specfact.08-simplify) that core docs now reference. Core consumers that parse ReviewFinding.category must accept the additional literal "ai_bloat" (schema add), and pre-commit/CLI behaviour expects .specfact/code-review.json to be present and include ai_bloat entries without causing blocking errors.
  • Verify core's ReviewFinding schema/parser accepts "ai_bloat" and that any scoring/filtering in core treats ai_bloat as score-neutral (or ignores it). (Evidence for needed compatibility exists in modules tests and design spec.) [::nold-ai/specfact-cli-modules::openspec/changes/code-review-ai-bloat-detection/specs/code-review-ai-bloat-detection/spec.md][::nold-ai/specfact-cli-modules::tests/unit/specfact_code_review/run/test_scorer.py]

🔇 Additional comments (8)

CHANGELOG.md (1)

13-27: LGTM!

pyproject.toml (1)

7-7: LGTM!

setup.py (1)

10-10: LGTM!

src/__init__.py (1)

6-6: LGTM!

src/specfact_cli/__init__.py (1)

48-48: LGTM!

README.md (1)

62-63: LGTM!

docs/index.md (1)

13-13: LGTM!

Also applies to: 37-38

docs/getting-started/quickstart.md (1)

15-15: LGTM!

Also applies to: 48-55