Update skill

[el-feo]

This pull request introduces a comprehensive integration of RubyCritic for Ruby code quality analysis, including workflow documentation, configuration references, and automated CI reporting. The changes aim to standardize quality checks, provide actionable feedback, and ensure maintainable code through both developer and CI workflows.

Documentation and Workflow Improvements:

• The .claude/skills/rubycritic/SKILL.md file has been extensively rewritten to clarify objectives, quick start instructions, workflow integration, error handling, git hooks, configuration, common usage patterns, code smell references, installation, and success criteria. The documentation now provides step-by-step guidance for running RubyCritic, interpreting results, and responding to issues, with links to detailed reference guides. [1] [2]

Reference and Configuration Enhancements:

• Added .claude/skills/rubycritic/references/configuration.md, a detailed guide covering advanced RubyCritic configuration options, usage patterns for different environments (strict, CI, legacy, development), command-line overrides, output formats, CI integration, score calculation, exclusion patterns, tool integration, troubleshooting, and best practices.

CI/CD Integration:

• Introduced .github/workflows/rubycritic.yml, a GitHub Actions workflow that automatically runs RubyCritic in CI mode on pull requests affecting Ruby files in the pdf_converter project. The workflow installs dependencies, runs RubyCritic, analyzes results, and posts a detailed quality report as a PR comment, including score breakdowns and recommendations. The HTML report is uploaded as an artifact for further review.

Automated Feedback and Best Practices:

• The CI workflow provides actionable feedback directly on pull requests, highlighting files needing attention, overall score, and recommendations based on quality thresholds. This encourages immediate remediation of code smells and complexity issues, supporting a culture of continuous improvement.

Reference Guides and Troubleshooting:

• All documentation sections now reference supporting guides for configuration, error handling, code smells, and git hooks, ensuring developers have access to troubleshooting and advanced usage information. [1] [2]

These changes collectively establish a robust framework for Ruby code quality management, making it easier for developers to maintain high standards and for teams to enforce quality gates in automated workflows.

[github-actions]

🔍 RubyCritic Code Quality Report

Overall Score: 🟢 87.7/100 (Good)

Quality Distribution

Grade	Files	Description
A	7	Excellent quality
B	4	Good quality
C	2	Fair quality
D	0	Poor quality
F	0	Critical issues

📋 Files Needing Attention

File	Score	Grade	Issues
app/image_uploader.rb	0.0	C	10
app/pdf_converter.rb	0.0	C	10

💡 Recommendations

• 🔹 Consider refactoring files with grade C or lower
• 🔹 Focus on reducing complexity in lower-scored files

---

📊 Full report available in the RubyCritic HTML output