Bluefin LTS — Skill Index#
Load only the skill for the task at hand. Skill files live in docs/skills/.
| Task | Skill file |
|---|---|
Local builds, validation, just recipes, variant map | skills/build.md |
| CI/CD workflows, publish logic, tag namespaces, pitfalls | skills/ci-cd.md |
| CentOS vs Fedora: packages, COPR, akmods, EPEL | skills/centos-vs-fedora.md |
| GNOME Shell extensions: add, remove, build patterns | skills/gnome-extensions.md |
| Release pipeline, rollback, registry, ISO status | skills/release.md |
| OEM hardware hooks, Framework/Ampere setup, hook architecture | skills/hardware.md |
Self-improvement mandate#
When you discover a non-obvious pattern, workaround, or convention:
- Find the relevant skill file in
docs/skills/. - Add the learning as a canonical pattern — not a session log. Write it as a rule or runbook entry a future agent would use directly.
- Remove or replace stale content that contradicts the new learning.
- Commit the skill update in the same PR as the change that prompted it.
Signs of a session log (don't do this):
- Section headers with
(added YYYY-MM-DD)dates - "In this session we found..." narrative phrasing
- Multiple versions of the same pattern coexisting
Signs of a good skill entry:
- Imperative runbook format: "When X, do Y"
- The broken pattern is removed or marked wrong, not preserved alongside the fix
- Commands are copy-pasteable and tested
For skill file format conventions, see:
projectbluefin/actions/.github/skills/skill-improvement/SKILL.md
