intel-canary

Lint code for macOS Intel portability and enforce CI pipeline checks.

1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielraffel/burl --skill intel-canary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: intel-canary
Source: https://github.com/danielraffel/burl/tree/main/.agents/skills/intel-canary
Command: npx skills add https://github.com/danielraffel/burl --skill intel-canary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, yamllint, actionlint, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The intel-canary skill addresses the issue of maintaining and verifying the portability of the Pulp framework to macOS Intel (x86_64) architecture, ensuring compatibility and functionality across different builds.

Core Features & Use Cases

  • Linting: Static analysis of the codebase to detect non-portable code patterns.
  • CI Tiering: CI pipeline steps that enforce portability checks at various levels of importance.
  • Allowlisting: Managing a whitelist of exceptions to the linting rules for genuinely arch-aware occurrences.
  • Documentation: Providing a guide on how the skill operates and how to use it effectively.
  • Use Case: Before merging a pull request, the intel-canary skill can be used to ensure that the changes do not break the portability of the Pulp framework on the macOS Intel platform.

Quick Start

Run the intel-canary skill to lint your code and check for portability issues.

Frequently Asked Questions about intel-canary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my code for macOS Intel portability issues before merging?▼

To check for macOS Intel portability issues, run the intel-canary skill to perform static code analysis and enforce CI pipeline checks for cross-arch build wiring. This ensures your changes do not break the Pulp framework's x86_64 compatibility.

What is CI tiering for cross-arch build configurations?▼

CI tiering for cross-arch build configurations enforces portability checks at various levels of importance within your CI pipeline. This mechanism ensures that changes do not negatively impact the cross-architecture build wiring of the Pulp framework.

Do I need Python3, yamllint, and actionlint to lint macOS Intel portability?▼

Yes, you need Python3, yamllint, and actionlint installed to lint macOS Intel portability. These dependencies execute the static code analysis scripts and validate the CI pipeline configurations for cross-arch build compatibility.

How do I manage exceptions for arch-aware code patterns during static code analysis?▼

You manage exceptions for arch-aware code patterns during static code analysis by using an allowlisting mechanism. This whitelist manages genuinely arch-aware occurrences, exempting them from the standard linting rules enforced by the CI pipeline.

Can I use static analysis to prevent breaking Pulp framework compatibility?▼

Yes, you can use static analysis to prevent breaking Pulp framework compatibility. The intel-canary skill detects non-portable code patterns and enforces CI pipeline checks to ensure changes maintain macOS Intel x86_64 architecture functionality.

Why does my CI pipeline fail on cross-arch build wiring changes?▼

Your CI pipeline fails on cross-arch build wiring changes because static code analysis detected non-portable code patterns. The CI tiering mechanism blocks merges that negatively impact macOS Intel portability unless explicitly allowlisted.