使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill lint开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
仓库原始内容
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Rails Linting Guide
Run linting tools and fix issues before pushing code.
Workflow
1. Check What Changed
bash
git diff --name-only HEAD~1
# or for unstaged changes
git diff --name-only2. Run Linters
Ruby files:
bash
# Check only
bundle exec rubocop
# Auto-fix
bundle exec rubocop -AERB templates:
bash
# Check only
bundle exec erblint --lint-all
# Auto-fix
bundle exec erblint --lint-all --autocorrectSecurity scan:
bash
bin/brakeman --no-pager3. Handle Results
If auto-fix worked:
bash
git add -A && git commit -m "style: linting"If manual fixes needed:
- Report specific issues with file:line references
- Suggest fixes for common patterns
4. Common Issues
| Issue | Fix |
|---|---|
| Line too long | Break into multiple lines |
| Missing frozenstringliteral | Add # frozen_string_literal: true at top |
| Trailing whitespace | Remove trailing spaces |
| Missing newline at EOF | Add blank line at end |
Output
markdown
## Linting Summary
### Ruby (rubocop)
- Files checked: X
- Offenses: X (Y auto-corrected)
- Remaining issues: [list with file:line]
### ERB (erblint)
- Files checked: X
- Issues: X (Y auto-corrected)
### Security (brakeman)
- Warnings: X
- Critical: [list if any]
### Status
[PASSED - ready to push / NEEDS ATTENTION - manual fixes required]
