An advanced markdown engine
tegwick
cbf82b74cb
Implemented comprehensive CLI naming consistency by standardizing all subsystem commands to use *-stats for status reporting: ## Changes Made: ### 1. Removed Unnecessary Skipped Tests - Removed two deferred tests for global option path display from Issue #39 - Tests were marked as requiring "complex CLI changes" and deemed not worth effort - Cleaner test suite without placeholder functionality ### 2. Renamed cache-info → cache-stats - Updated CLI command: @cli.command('cache-stats') - Updated function name: cache_info() → cache_stats() - Updated all test files to use cache-stats - Consistent with subsystem naming convention ### 3. Renamed db-status → db-stats - Updated CLI command: @cli.command('db-stats') - Updated function name: db_status() → db_stats() - Updated all test files and references to use db-stats - Maintains database subsystem consistency ### 4. Implemented config-stats Command - New CLI command following *-stats convention - Displays configuration statistics and status information - Supports all output formats: table, json, yaml, simple - Integrates with existing config system when available - Provides fallback functionality for basic configuration reporting ## Established Convention: All CLI subsystems now have consistent *-stats commands: - ✅ ast-stats (already existed) - ✅ cache-stats (renamed from cache-info) - ✅ db-stats (renamed from db-status) - ✅ config-stats (newly implemented) ## Benefits: - Intuitive command discovery (users know to try *-stats for any subsystem) - Consistent CLI experience across all subsystems - Better organized help documentation - Professional CLI interface following standard conventions All tests updated and passing. CLI maintains backward compatibility for essential functionality while establishing clear, consistent patterns. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .claude/agents | ||
| .github/workflows | ||
| .venv_old | ||
| application | ||
| cli | ||
| config | ||
| diary | ||
| docs | ||
| domain | ||
| gitea | ||
| infrastructure | ||
| markitect | ||
| services | ||
| tddai | ||
| tests | ||
| wiki@648d8247c4 | ||
| .env.tddai | ||
| .gitignore | ||
| .gitmodules | ||
| ARCHITECTURAL_CHAOS_TESTING_ISSUE.md | ||
| ARCHITECTURE.md | ||
| CAPABILITIES.md | ||
| CONFIG.md | ||
| DATA_ACCESS_IMPROVEMENTS_GAMEPLAN.md | ||
| DIRECTORY_STRUCTURE_OPTIMIZATION_GAMEPLAN.md | ||
| DOMAIN_LOGIC_SEPARATION_DEMO.md | ||
| DOMAIN_LOGIC_SEPARATION_GAMEPLAN.md | ||
| ERROR_HANDLING_GUIDE.md | ||
| FEATURES.md | ||
| GITEA_INTEGRATION_CONSOLIDATION_GAMEPLAN.md | ||
| gitea_issue_body.txt | ||
| install-claude.sh | ||
| install-cursor.sh | ||
| install-depends.sh | ||
| install-nvm.sh | ||
| install-pip.sh | ||
| LEGACY_AGENT_GUIDE.md | ||
| LEGACY_COMPATIBILITY_SYSTEM.md | ||
| MAIN_BRANCH_OPTIMIZATION_GAMEPLAN.md | ||
| Makefile | ||
| NEXT.md | ||
| ProjectDiary.md | ||
| ProjectStatusDigest.md | ||
| pyproject.toml | ||
| README.md | ||
| RelevantClaudeIssues.md | ||
| retrieved_roundtrip.md | ||
| ROADMAP.md | ||
| run_architectural_tests.py | ||
| run_randomized_tests.py | ||
| schema_summary.py | ||
| tddai-setup.sh | ||
| tddai_cli.py | ||
| tddai_issue_body.txt | ||
| TEST_ARCHITECTURE.md | ||
| test_frontmatter.md | ||
| test_roundtrip.md | ||
| test_status_report.md | ||
| TESTING_ARCHITECTURE_ENHANCEMENT_GAMEPLAN.md | ||
| visualize_schema.py | ||
MarkiTect - Advanced Markdown Engine
Your Markdown, Redefined.
MarkiTect transforms markdown from plain text into intelligent, structured data with performance optimization, schema validation, and relational querying capabilities. Stop treating documentation as text files—start managing it as a database.
Key Features:
- Lightning Performance: 60-85% faster document processing through intelligent AST caching
- Schema Validation: Enforce document structure and consistency
- Database Integration: Query markdown content with SQL-like operations
- CLI Tools: Complete command-line interface for automation and workflows
📚 Documentation
Quick Start: Getting Started · Command Reference
Architecture: Caching System · Performance Philosophy
Development: TDD Workflow · Contributing
Project Status: Current Status · Roadmap · Next Actions