Synchronize the Fizz harness with changed Solidity source trees.
npx skills add https://github.com/pashov/skills --skill fizz-sync
Please help me install this Agent Skill. Skill: fizz-sync Source: https://github.com/pashov/skills/tree/main/fizz/skills/fizz-sync Command: npx skills add https://github.com/pashov/skills --skill fizz-sync
This Skill ensures that the Fizz harness is up-to-date with changes in the source tree, optimizing the fuzzing process by detecting drift, quarantining stale properties, regenerating handler stubs, and refreshing the snapshot.
fizz-sync can be triggered to ensure that the fuzzing harness is still in sync without re-running the full pipeline.Run the fizz-sync skill to synchronize the Fizz harness with your changed source tree.
High-intent search queries and answers about installing and using this skill.
Synchronizing a fuzzing harness after modifying Solidity sources involves detecting contract drift, quarantining stale properties, regenerating handler stubs, and refreshing the snapshot to ensure harness consistency without re-running the full pipeline.
When the Solidity source tree changes, invalid fuzzing properties are identified and placed into a stale property quarantine. This ensures outdated assertions do not break the fuzzing harness synchronization process.
Yes, you need the Fizz skill installed. Synchronizing the Fizz harness requires direct access to the Fizz skill itself and its associated metadata directories to successfully detect and address drift in Solidity contracts.
Fuzzing harness drift occurs because added, removed, or changed Solidity contract functions create inconsistencies between the source tree and the harness. Reconciliation detects these modifications to regenerate drifted handler stubs.
Yes, you can refresh the fuzzing snapshot without re-running the full pipeline. The synchronization process detects source tree drift and refreshes the snapshot with the latest harness state, optimizing the fuzzing workflow.
The best way to handle added or removed functions in a Solidity fuzzing harness is through source tree reconciliation. This detects contract function changes, regenerates drifted handler stubs, and quarantines stale properties automatically.
sablier-labsGenerate Bulloak .tree files for Solidity smart contract integration tests.
elizaOSAnalyze code coverage from fuzzing campaigns using llvm-cov and gcovr.
nirholasCompile, deploy, and interact with Solidity contracts in a browser.
allanninalSet up and run continuous fuzzing for open-source projects with OSS-Fuzz.