Automated summary
Uses ProviderObserver to log or debug Riverpod provider lifecycle events.
Strengths
- Enables centralized logging of provider state changes
- Works with any Riverpod provider
- Supports custom analytics integration
- Named providers provide clearer logs
Limitations
- May not capture in-place mutations accurately
- Requires manual setup for code-generated providers
- Performance impact if logging is verbose in production
When you need to track provider state changes for debugging, analytics, or monitoring in a Riverpod application.
For simple apps where provider state is trivial and logging is unnecessary.
Security analysis
SafeNo execution risk; skill only describes a debugging pattern in Dart.
No concerns found
How this analysis is madeExamples
Show me how to create a ProviderObserver that logs provider state changes in Riverpod.How can I debug changes to a specific Riverpod provider using ProviderObserver?I want to use Riverpod ProviderObserver to send analytics events when providers update. Give me an example.name: riverpod-observers description: Use ProviderObserver to log or debug Riverpod provider lifecycle; didUpdateProvider, ProviderScope observers, naming providers. Use when adding logging, analytics, or debugging for provider state changes. Use this skill when the user asks about ProviderObserver, logging Riverpod, or debugging provider updates.
Riverpod — ProviderObservers
Instructions
A ProviderObserver receives lifecycle events for providers (e.g. when a provider's value changes). Use it for logging, analytics, or debugging.
Implementing an observer
Extend ProviderObserver and override the methods you need (e.g. didUpdateProvider). Pass instances to ProviderScope or ProviderContainer via the observers parameter.
Example: logger
final class Logger extends ProviderObserver {
@override
void didUpdateProvider(
ProviderObserverContext context,
Object? previousValue,
Object? newValue,
) {
print('{"provider": "${context.provider}", "newValue": "$newValue"}');
}
}
void main() {
runApp(
ProviderScope(
observers: [Logger()],
child: const MyApp(),
),
);
}
Naming providers
For clearer logs, give providers a name:
final myProvider = Provider<int>((ref) => 0, name: 'MyProvider');
With code generation, a name is usually assigned automatically.
Note on mutations
If state is mutated in place (e.g. a List with ref.notifyListeners), previousValue and newValue in didUpdateProvider may be the same reference. For distinct values, clone before mutating.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/riverpod-providerobservers-mmlj2p41/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/riverpod-providerobservers-mmlj2p41' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/riverpod-providerobservers-mmlj2p41/download' --output '.skill-downloads/riverpod-providerobservers-mmlj2p41/SKILL.md.part' && mv '.skill-downloads/riverpod-providerobservers-mmlj2p41/SKILL.md.part' '.skill-downloads/riverpod-providerobservers-mmlj2p41/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/riverpod-providerobservers-mmlj2p41/SKILL.md' && test -s '.skill-downloads/riverpod-providerobservers-mmlj2p41/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/riverpod-observers' && cp -R '.skill-downloads/riverpod-providerobservers-mmlj2p41' '.claude/skills/riverpod-observers'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/riverpod-providerobservers-mmlj2p41'openskills read 'riverpod-providerobservers-mmlj2p41'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/riverpod-providerobservers-mmlj2p41/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.