lineageos
Use when working with LineageOS custom ROM development, including syncing sources, building, device trees, repopick, Gerrit contributions, or LineageOS-specific features. Triggers on "LineageOS", "lineage-sdk", "breakfast", "brunch", "repopick", "vendor/lineage", "lineage.dependencies", "mka bacon".
What this skill does
# LineageOS Development
This skill covers LineageOS custom ROM development - from syncing sources to building and contributing.
## Getting Started
### Initialize Source
```bash
mkdir ~/lineage && cd ~/lineage
# Install repo (if needed)
mkdir -p ~/.bin
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/.bin/repo
chmod a+x ~/.bin/repo
export PATH="$HOME/.bin:$PATH"
# Init LineageOS 21 (Android 14)
repo init -u https://github.com/LineageOS/android.git -b lineage-21.0 --git-lfs
# Sync
repo sync -c -j$(nproc) --force-sync --no-tags --no-clone-bundle
```
### Build Commands
```bash
# Setup environment
source build/envsetup.sh
# Setup device (syncs device repos too)
breakfast <device>
# Build flashable ZIP
brunch <device>
# Or separately:
breakfast <device>
mka bacon
# Output: out/target/product/<device>/lineage-21.0-*-UNOFFICIAL-<device>.zip
```
---
## Essential Commands
| Command | Purpose |
| -------------------- | -------------------------------- |
| `breakfast <device>` | Setup device + sync dependencies |
| `brunch <device>` | breakfast + full build |
| `mka bacon` | Build flashable ZIP |
| `mka bootimage` | Build kernel only |
| `mka systemimage` | Build system only |
| `repopick <change>` | Cherry-pick from Gerrit |
---
## Device Trees
### Required Files
```
device/<vendor>/<device>/
├── lineage_<device>.mk # Product makefile
├── lineage.dependencies # Repo dependencies
├── vendorsetup.sh # Add to lunch
├── BoardConfig.mk # Hardware config
├── device.mk # Packages and configs
└── extract-files.sh # Vendor blob extraction
```
### lineage\_<device>.mk
```makefile
# Inherit device
$(call inherit-product, device/vendor/device/device.mk)
# Inherit LineageOS common
$(call inherit-product, vendor/lineage/config/common_full_phone.mk)
PRODUCT_NAME := lineage_device
PRODUCT_DEVICE := device
PRODUCT_BRAND := Vendor
PRODUCT_MODEL := Device Name
PRODUCT_MANUFACTURER := Vendor
```
### lineage.dependencies
```json
[
{
"repository": "android_kernel_vendor_device",
"target_path": "kernel/vendor/device"
},
{
"repository": "android_device_vendor_device-common",
"target_path": "device/vendor/device-common"
},
{
"repository": "proprietary_vendor_device",
"target_path": "vendor/device"
}
]
```
---
## repopick - Cherry-picking from Gerrit
```bash
# Single change
repopick 12345
# Multiple changes
repopick 12345 12346 12347
# By topic
repopick -t feature-topic
# With dependencies
repopick -Q 12345
# Force overwrite local changes
repopick -f 12345
# Show what would be picked
repopick -n 12345
```
### Find Change Numbers
1. Go to `https://review.lineageos.org`
2. Search for changes
3. Change number is in the URL or displayed
---
## Vendor Blobs
### Extract from Device
```bash
cd device/vendor/device
./extract-files.sh
```
### Extract from OTA/Factory Image
```bash
./extract-files.sh ~/Downloads/ota.zip
```
### proprietary-files.txt Format
```txt
# Audio HAL
vendor/lib64/hw/audio.primary.platform.so
vendor/etc/audio_policy_configuration.xml
# With destination path
vendor/lib64/lib.so:vendor/lib64/libfoo.so
# From another device
vendor/lib64/lib.so|other_device
```
---
## LineageOS Features
### Trust Interface
Security dashboard showing device integrity:
```makefile
# device.mk
PRODUCT_PACKAGES += \
LineageTrust
```
### LiveDisplay
Hardware-accelerated display tuning:
```makefile
PRODUCT_PACKAGES += \
[email protected]
```
### Styles / Themes
System theming support:
```makefile
PRODUCT_PACKAGES += \
ThemePicker
```
---
## Key Directories
| Path | Purpose |
| --------------------------- | ------------------- |
| `vendor/lineage/` | LineageOS additions |
| `lineage-sdk/` | LineageOS SDK |
| `device/<vendor>/<device>/` | Device tree |
| `kernel/<vendor>/<device>/` | Kernel source |
| `vendor/<vendor>/` | Proprietary blobs |
---
## Contributing
### Setup Gerrit Access
```bash
git config --global review.review.lineageos.org.username <username>
```
### Submit Change
```bash
# Create branch
repo start my-feature .
# Make changes
git add -A
git commit -m "subsystem: Short description
Detailed explanation.
Change-Id: <auto-generated>"
# Push for review
git push ssh://<username>@review.lineageos.org:29418/<project> HEAD:refs/for/<branch>
```
### Commit Message Format
```
subsystem: Short description
Longer explanation wrapped at 72 characters.
Explain why, not what.
Change-Id: I1234567890abcdef...
```
---
## Common Issues
### Breakfast Fails - Missing Repos
```bash
# Re-sync device tree
repo sync device/vendor/device kernel/vendor/device vendor/device
```
### Build Fails - SELinux
```bash
# Find denials
adb shell dmesg | grep "avc: denied"
# Generate policy (on host)
adb shell dmesg | audit2allow -p out/target/product/<device>/root/sepolicy
```
### Missing Blobs
Check logcat for:
```
E linker: cannot find symbol...
E ServiceManager: Could not find service...
```
Add missing files to `proprietary-files.txt` and re-extract.
---
## Quick Reference
```bash
# Full workflow
source build/envsetup.sh
breakfast cheeseburger
brunch cheeseburger
# Just kernel
mka bootimage
# Cherry-pick fix
repopick 12345
# Sync everything
repo sync -c -j$(nproc)
# Sync one project
repo sync packages/apps/Settings
# Clean build
m clean && brunch <device>
```
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.