chore(giskard-scan): migrate generate_suite and generators from giskard-checks" - #2506
Merged
Conversation
…pace Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…r base classes Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copy prompt_injection.jsonl, adversarial.j2, llm01_indirect_injection.j2, and generation_rules.j2 into giskard-scan; add PromptInjectionScenarioGenerator and AdversarialScenarioGenerator with giskard.scan:: prompt namespaces. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…to giskard.scan::
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…scan Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…gistry test - Restore Scenario/Trace imports and typed return on _generate_scenarios - Restore full NumPy docstring on generate_suite - Add DatasetScenarioGenerator inheritance note to PromptInjectionScenarioGenerator - Fix test_suite_generator_registry_exported_from_top_level to import from giskard.scan Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…nslator - restore isinstance guard in SuiteGeneratorRegistry.register() (was silently dropped) - replace manual enumerate/del loop in unregister() with list.remove() - unify serialize_user_message into single return path via parts variable - collapse _get_name_from_call_id to a single dict.get chain - replace two-pass list comprehension in part_content_to_giskard_messages with single-pass loop - hoist _rule_generation_pipeline() before retry loop in _generate_rules Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
giskard-scanpackage (libs/giskard-scan) owning all generation machinery:ScenarioGenerator,DatasetScenarioGenerator,AdversarialScenarioGenerator,PromptInjectionScenarioGenerator,SuiteGeneratorRegistry, andgenerate_suitescenarios_generator/sub-package and moved prompt templates fromgiskard-checks— it is now a pure eval/assertion library (breaking change:from giskard.checks import generate_suiteraisesImportError)Makefile, CI matrix, release workflow,pyrightconfig.json, PR labeler, andREADME.mdto includegiskard-scanRelated Issue
Type of Change
Coding agents
Autonomous agents with no human in the loop must read AUTONOMOUS.md before opening a PR.
PR title: agent-opened PRs must end the title with
🤖🤖🤖🤖(exactly four robot emojis). Do not omit — that suffix is how the expedited agent PR workflow picks up the PR.Checklist
CODE_OF_CONDUCT.mddocument.CONTRIBUTING.mdguide.uv.lockrunninguv lock(only applicable whenpyproject.tomlhas beenmodified)