rubocop-integration
Use when ruboCop CI integration including GitHub Actions, plugins, and performance optimization.
What this skill does
# rubocop integration
Master RuboCop CI integration including GitHub Actions, plugins, and performance optimization. This skill provides comprehensive coverage of essential concepts, patterns, and best practices for professional RuboCop development.
## Overview
RuboCop is a powerful tool for ruby development, providing robust capabilities for maintaining code quality and ensuring reliable software delivery. This skill covers the fundamental through advanced aspects of working with RuboCop.
## Installation and Setup
### Basic Installation
Setting up RuboCop requires proper installation and configuration in your development environment.
```bash
# Installation command specific to RuboCop
# Follow official documentation for latest version
```
### Project Configuration
Create appropriate configuration files and setup for your project structure:
- Configuration file setup
- Project structure organization
- Team collaboration setup
- CI/CD integration preparation
## Core Concepts
### Fundamental Principles
Understanding the core principles of RuboCop is essential for effective usage:
1. **Architecture** - How RuboCop is structured and operates
2. **Configuration** - Setting up and customizing behavior
3. **Integration** - Working with other tools and frameworks
4. **Best Practices** - Industry-standard approaches
### Key Features
RuboCop provides several key features that make it valuable:
- Feature 1: Core functionality
- Feature 2: Advanced capabilities
- Feature 3: Integration options
- Feature 4: Performance optimization
- Feature 5: Extensibility
### Configuration Strategy
Proper configuration ensures RuboCop works optimally:
- Environment-specific setup
- Team standards enforcement
- Performance tuning
- Error handling configuration
### Advanced Usage
For complex scenarios, RuboCop offers advanced capabilities:
- Custom extensions
- Advanced patterns
- Performance optimization
- Scalability considerations
## Code Examples
### Example 1: Basic Setup
```ruby
// Basic RuboCop setup
// Demonstrates fundamental usage patterns
// Shows proper initialization and configuration
// Core setup code
function basicSetup() {
// Initialize framework
// Configure basic options
// Return configured instance
}
// Usage example
const instance = basicSetup();
```
### Example 2: Configuration
```ruby
// Configuration example for RuboCop
// Shows how to properly configure
// Includes common options and patterns
// Configuration object
const config = {
option1: 'value1',
option2: 'value2',
advanced: {
setting1: true,
setting2: false
}
};
// Apply configuration
function applyConfig(config) {
// Validation logic
// Application logic
// Return result
}
```
### Example 3: Advanced Pattern
```ruby
// Advanced usage pattern
// Demonstrates sophisticated techniques
// Shows best practices in action
function advancedPattern() {
// Setup phase
// Execution phase
// Cleanup phase
}
```
### Example 4: Integration
```ruby
// Integration with other tools
// Shows real-world usage
// Demonstrates interoperability
function integrationExample() {
// Setup integration
// Execute workflow
// Handle results
}
```
### Example 5: Error Handling
```ruby
// Proper error handling approach
// Defensive programming patterns
// Graceful degradation
function withErrorHandling() {
try {
// Main logic
} catch (error) {
// Error recovery
} finally {
// Cleanup
}
}
```
### Example 6: Performance Optimization
```ruby
// Performance-optimized implementation
// Shows efficiency techniques
// Demonstrates best practices
function optimizedApproach() {
// Efficient implementation
// Resource management
// Performance monitoring
}
```
### Example 7: Testing
```ruby
// Testing approach for RuboCop
// Unit test examples
// Integration test patterns
function testExample() {
// Test setup
// Execution
// Assertions
// Teardown
}
```
### Example 8: Production Usage
```ruby
// Production-ready implementation
// Includes monitoring and logging
// Error recovery and resilience
function productionExample() {
// Production configuration
// Monitoring setup
// Error handling
// Logging
}
```
## Best Practices
1. **Follow conventions** - Adhere to established naming and structural patterns for consistency
2. **Configure appropriately** - Set up framework configuration that matches project requirements
3. **Validate inputs** - Always validate and sanitize inputs before processing
4. **Handle errors gracefully** - Implement comprehensive error handling and recovery
5. **Document decisions** - Comment configuration choices and non-obvious implementations
6. **Test thoroughly** - Write comprehensive tests for all functionality
7. **Optimize performance** - Profile and optimize critical paths
8. **Maintain security** - Follow security best practices and guidelines
9. **Keep updated** - Regularly update framework and dependencies
10. **Monitor production** - Implement logging and monitoring for production systems
## Common Pitfalls
1. **Incorrect configuration** - Misconfiguration leads to unexpected behavior and bugs
2. **Missing error handling** - Not handling edge cases causes production issues
3. **Poor performance** - Not optimizing leads to scalability problems
4. **Inadequate testing** - Insufficient test coverage misses bugs
5. **Security vulnerabilities** - Not following security best practices exposes risks
6. **Tight coupling** - Poor architecture makes maintenance difficult
7. **Ignoring warnings** - Dismissing framework warnings leads to future problems
8. **Outdated dependencies** - Using old versions exposes security risks
9. **No monitoring** - Lack of observability makes debugging difficult
10. **Inconsistent standards** - Team inconsistency reduces code quality
## Advanced Topics
### Customization
RuboCop allows extensive customization for specific needs:
- Custom plugins and extensions
- Behavior modification
- Integration adapters
- Domain-specific adaptations
### Performance Tuning
Optimize RuboCop performance for production:
- Profiling and benchmarking
- Resource optimization
- Caching strategies
- Parallel execution
### CI/CD Integration
Integrate RuboCop into continuous integration pipelines:
- Automated execution
- Result reporting
- Quality gates
- Deployment integration
### Troubleshooting
Common issues and their solutions:
- Configuration errors
- Integration problems
- Performance issues
- Unexpected behavior
## When to Use This Skill
- Setting up RuboCop in new projects
- Configuring RuboCop for specific requirements
- Migrating to RuboCop from alternatives
- Optimizing RuboCop performance
- Implementing advanced patterns
- Troubleshooting RuboCop issues
- Integrating RuboCop with CI/CD
- Training team members on RuboCop
- Establishing team standards
- Maintaining existing RuboCop implementations
## Additional Resources
### Documentation
- Official RuboCop documentation
- Community guides and tutorials
- API reference materials
- Migration guides
### Tools and Utilities
- Development tools
- Testing utilities
- Monitoring solutions
- Helper libraries
### Community
- Online forums and communities
- Open source contributions
- Best practice repositories
- Example implementations
## Conclusion
Mastering RuboCop requires understanding both fundamentals and advanced concepts. This skill provides the foundation for professional-grade usage, from initial setup through production deployment. Apply these principles consistently for best results.
## Detailed Configuration Examples
### Configuration Option 1
Comprehensive configuration example demonstrating best practices and common patterns used in production environments.
```bash
# Detailed configuration setup
# Includes all necessary options
# Optimized for production use
```
### Configuration Option 2
Alternative configuration approach for different use cases, showing flexibility and adapRelated in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.