Playbook: default (fallback)
SkillDev toolsFallback Renovate maintenance playbook, read by the `/fix` skill when no other `renovate-*` playbook matches a red Renovate dependency PR. Carries repository-wide conventions only (no dependency-specific knowledge). Use for mechanical dependency drift: a stale-generated-code `make generate` diff, `go mod tidy` / `make tidy-all` dropping a just-added require on a Go major-version import-path migration (the require is unused until imports are rewritten), a `make crosslink` replace-directive change, or a new lint failure. Select this only when the PR is NOT the otel collector core/contrib lockstep group (use `renovate-otel-core`) and does NOT surface semantic-convention breakage (use `renovate-semconv`).
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Playbook: default (fallback) skill
What this skill tells your AI
The instructions your AI receives, as published by liatrio/liatrio-otel-collector in .claude/skills/renovate-default/SKILL.md and read by ahel’s review.
The fallback playbook used when a Renovate PR matches no group label and no other
playbook's package globs. It carries only repository-wide conventions — it deliberately holds no
dependency-specific knowledge. When you find yourself repeatedly hand-holding a class of bump that
lands here, that is the signal to add a dedicated renovate-* playbook-skill.
Authoritative docs
Read these before changing anything; they are the source of truth this playbook refuses to duplicate:
AGENTS.md— repository conventions, the codegen pipelines, the multi-module layout, and the Guardrails section.AGENTS.md→ Common commands — themaketargets (generate,tidy-all,crosslink,lint-all,test-all,build) a fix must keep green.docs/semantic-conventions.md— only relevant if the bump surfaces a semconv migration; if so, switch torenovate-semconv.
Failure modes → remediation
| Failure signature | Likely cause | Remediation |
|---|---|---|
make generate produces a diff | stale generated code after a dependency or metadata.yaml-adjacent change | run make generate and commit the regenerated files (never hand-edit generated_*.go / documentation.md) |
go mod tidy / make tidy-all drops a just-added require | a major Go module bump is an import-path migration; the new path is unused until imports are rewritten | do not accept the drop — rewrite import paths to the new major version first, then tidy (see renovate-otel-core for the lockstep variant) |
make crosslink changes replace directives | module wiring drifted | commit the crosslink result; if a component was added/removed, config/manifest.yaml also needs editing |
| lint failure new to this PR | formatting or a newly-flagged construct | run the module-local make fmt / make lint; fix only what the bump introduced |
Hard invariants / guardrails
These are non-negotiable regardless of which dependency triggered the PR:
- Never hand-edit generated files — change the source (
metadata.yaml,.graphql, genqlient config) and regenerate. SeeAGENTS.md→ Guardrails. - Never
git commit --no-verify— the conventional-commit andcheck-generatehooks must run. - Never touch
.github/**during a fix. - Never work on
main— fixes land on the PR'srenovate/**branch only. - Do not bump the semconv package as a side effect — it is a deliberate manual migration
(
docs/semantic-conventions.md). - Keep commits concern-separated: regeneration in one commit, mechanical adaptation in another.
Signals
- GitHub stars
- 47
- Forks
- 9
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
renovate-default- Source
- github.com/liatrio/liatrio-otel-collector