agentleFS
projectbluefinprojectbluefin/finpilot/.agents/skills/troubleshooting/SKILL.md

troubleshooting

Skill131 starsChanged 18 days agoApache-2.0View on GitHub

Symptom to cause to fix for build, CI, and runtime failures, plus the pre-commit checklist. Use when something is broken or before opening a pull request.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use task-breakdown and architecture.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ttmouseSkill

    task-breakdown

    专业的任务拆解器,将复杂需求拆分成"独立可运行与可演示"的最小闭环任务卡。严格按照纵向切片、单一数据变化、单一入口原则,确保每张任务卡都能在单回合实现并验证。当用户说"帮我拆解一下任务"、"用任务拆解器分析"、"按规范拆分"或需要将一个大的开发需求拆分成可执行的小任务时使用。输出格式严格按照[src/renderer/TODO.md]标准存储。

    Also in 3 projects that use this

  • AnthropicSkill

    architecture

    Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When a fix here was non-obvious, put it in the skill that owns the area, in the same pull request.

    line 53

“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Troubleshooting

Before a pull request

  • Conventional Commit message.
  • just lint — shellcheck on every tracked script.
  • just check — Justfile syntax.
  • just test-unit — the suite.
  • just validate-brewfiles / just validate-flatpaks if those changed.
  • just build if the image changed.

CI runs the same checks; running them locally only makes the pull request quiet.

Build

SymptomCauseFix
bootc container lint fails on a nonempty /runa script wrote to /run into an image layerremove it in 90-cleanup.sh; that phase deliberately does not mount /run as tmpfs
a third-party repository is live in the final imagea script enabled it and did not disable ituse copr_install_isolated, or disable it explicitly
the package layer rebuilds on every overlay editpackages drifted into the overlay phasekeep packages in 20-packages-and-services.sh
hadolint flags the Containerfilea rule in .github/hadolint.yamlfix it, or add a suppression with a reason

CI

SymptomCauseFix
validate never runsbranch protection names a check no workflow producesthe context must be exactly validate
Renovate logs a skip and opens nothingRENOVATE_TOKEN is not setexpected; set the secret to turn Renovate on
Renovate fails on Validate RENOVATE_TOKENthe token is expired or lacks the workflow scoperecreate the token
the promotion PR never opensstable does not existcreate the branch
the promotion PR will not mergestable requires an approvalset required approvals to 0
a Renovate PR waits foreverauto-merge is offenable it in Settings

Runtime

The two most common first-boot surprises — no Flatpaks, and no brew — are in the README's Troubleshooting section.

SymptomCauseFix
ujust shows no custom commands60-custom.just was not written or importedcheck that 10-overlay.sh copied the recipes

Capturing what you learned

When a fix here was non-obvious, put it in the skill that owns the area, in the same pull request. That is the only home for durable learning.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.