docs: skill documents Stryker as the repo's mutation runner - #97
Conversation
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
✅ Deploy Preview for moderaty ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Review limit reached
Next review available in: 38 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Sequence DiagramThis PR documents StrykerJS as the required mutation-testing runner for the Moderaty repository. The flow prepares a fresh checkout, runs Stryker with an explicit scope, and requires manual verification of surviving mutants. sequenceDiagram
participant Developer
participant Repository
participant StrykerJS
participant Vitest
Developer->>Repository: Run SvelteKit sync
Repository-->>Developer: Generate test configuration
Developer->>StrykerJS: Run scoped mutation audit
StrykerJS->>Vitest: Execute tests against mutants
Vitest-->>StrykerJS: Test results
StrykerJS-->>Developer: Mutation report and survivors
Developer->>Developer: Verify survivors by hand
Generated by CodeAnt AI |
There was a problem hiding this comment.
This documentation change is clean and ready to merge. The new section effectively documents the Stryker mutation testing setup for the repository, providing clear prerequisites, commands, and usage guidelines.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
|
🏁 CodeAnt Quality Gate ResultsCommit: ✅ Overall Status: PASSEDQuality Gate Details
|
PR Summary by QodoDocument StrykerJS as Moderaty’s mutation runner in mutation-testing skill
AI Description
High-Level Assessment
Files changed (1)
|
Up to standards ✅🟢 Issues
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTo customize comments, go to the Qodo configuration screen, or learn more in the docs. |
Review triage — no actionable findings@qodo-code-review — 0 bugs / 0 rule violations / 0 requirement gaps. Nothing to fix. Docs-only change (skill SKILL.md); holding for human review. |
|
Tip For best results, initiate chat on the files or code changes.
You are interacting with an AI system. |
|
Question: ## review triage — no actionable findings @qodo-code-review — 0 bugs / 0 rule violations / 0 requirement gaps. nothing to fix. docs-only change (skill skill.md); holding for human review. Answer: The added section correctly documents the repository-specific StrykerJS workflow:
The change is documentation-only, focused, and consistent with the stated requirements. |
No actionable Qodo findings are present. This is a documentation-only update adding Moderaty-specific Stryker usage guidance, so no code fix is needed; human review can proceed. |
Triage closed@CodeAnt-AI, @qodo-code-review, @coderabbitai — thanks for confirming no actionable findings. Docs-only; holding for human review. |
|
Tip For best results, initiate chat on the files or code changes.
🐇 You are interacting with an AI system. |
|
Question: ## triage closed ****, @qodo-code-review, @coderabbitai — thanks for confirming no actionable findings. docs-only; holding for human review. Answer:
The change is suitable for human review. |
Acknowledged—no actionable findings from my review. The documentation-only change is ready for human review. |




User description
What
Adds an "In the Moderaty repo — use Stryker" section to the mutation-testing skill (
SKILL.md, right after the core workflow), so the skill itself — not just AGENTS.md — tells the agent to use the installed StrykerJS for every mutation run:@stryker-mutator/core+@stryker-mutator/vitest-runner, configured by the barestryker init-generatedstryker.config.json— nomutateglobs or thresholds, so always pass an explicit scope.npx svelte-kit sync(Stryker's vitest runner crashes with a rolldown "Tsconfig not found" error without the generated.svelte-kit/tsconfig.json— reproduced in practice).--mutateaudits,--since mainfor PR-scale,--incrementalfor the cache.thresholds.breakCI ratchet stays a separate, maintainer-approved step.The generic tool guidance in
references/tools-by-language.mdalready covers StrykerJS in depth and is unchanged. Complements #94 (same facts in AGENTS.md).Installed copy re-synced to
~/.agents/skills/mutation-testing(diff-verified).Verification
codacy-analysis analyze --files .agents/skills-src/mutation-testing/SKILL.md— 0 issues.CodeAnt-AI Description
Document StrykerJS as the standard mutation-testing workflow for the Moderaty repository
What Changed
Impact
✅ Consistent mutation-testing workflow✅ Fewer mutation-test setup failures✅ Faster repeat mutation runs💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.