Skip to content

docs: skill documents Stryker as the repo's mutation runner - #97

Merged
Bonobo791 merged 1 commit into
mainfrom
docs-skill-stryker
Aug 5, 2026
Merged

docs: skill documents Stryker as the repo's mutation runner#97
Bonobo791 merged 1 commit into
mainfrom
docs-skill-stryker

Conversation

@Bonobo791

@Bonobo791 Bonobo791 commented Aug 5, 2026

Copy link
Copy Markdown
Owner

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 bare stryker init-generated stryker.config.json — no mutate globs or thresholds, so always pass an explicit scope.
  • Fresh-checkout/worktree prerequisite: 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).
  • Commands: scoped --mutate audits, --since main for PR-scale, --incremental for the cache.
  • Discipline reminders: verify survivors by hand; thresholds.break CI ratchet stays a separate, maintainer-approved step.

The generic tool guidance in references/tools-by-language.md already 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.
  • Docs-only change; no code paths touched.

CodeAnt-AI Description

Document StrykerJS as the standard mutation-testing workflow for the Moderaty repository

What Changed

  • The mutation-testing guide now directs contributors and agents to use the repository’s installed StrykerJS setup
  • Added setup guidance for fresh checkouts, including generating the required SvelteKit files before running mutation tests
  • Added commands for module-scoped audits, pull-request-sized runs, and incremental reruns
  • Clarified that mutation survivors require manual review and that CI thresholds need maintainer approval

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:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

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:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

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.

@cla-bot cla-bot Bot added the cla-signed label Aug 5, 2026
@codeant-ai

codeant-ai Bot commented Aug 5, 2026

Copy link
Copy Markdown

🤖 CodeAnt AI — Review Status

Status Commit Started (UTC) Finished (UTC)
✅ Reviewed your PR 4dfad96 Aug 05, 2026 · 14:12 14:12

@codeant-ai

codeant-ai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@netlify

netlify Bot commented Aug 5, 2026

Copy link
Copy Markdown

Deploy Preview for moderaty ready!

Name Link
🔨 Latest commit 4dfad96
🔍 Latest deploy log https://app.netlify.com/projects/moderaty/deploys/6a7344b7ac406c0008183530
😎 Deploy Preview https://deploy-preview-97--moderaty.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 79
Accessibility: 97
Best Practices: 100
SEO: 100
PWA: -
View the detailed breakdown and full score reports
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@Bonobo791, you've reached your PR review limit, so we couldn't start this review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: f006ee11-2bcf-4978-872e-27a3ae604dbe

📥 Commits

Reviewing files that changed from the base of the PR and between 2868fb6 and 4dfad96.

📒 Files selected for processing (1)
  • .agents/skills-src/mutation-testing/SKILL.md

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codeant-ai codeant-ai Bot added the size:S This PR changes 10-29 lines, ignoring generated files label Aug 5, 2026
@codeant-ai

codeant-ai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Sequence Diagram

This 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
Loading

Generated by CodeAnt AI

@amazon-q-developer amazon-q-developer Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@sonarqubecloud

sonarqubecloud Bot commented Aug 5, 2026

Copy link
Copy Markdown

@codeant-ai

codeant-ai Bot commented Aug 5, 2026

Copy link
Copy Markdown

🏁 CodeAnt Quality Gate Results

Commit: 4dfad961
Scan Time: 2026-08-05 14:12:47 UTC

✅ Overall Status: PASSED

Quality Gate Details

Quality Gate Status Details
Secrets ✅ PASSED 0 secrets found
Duplicate Code ✅ PASSED 0.0% duplicated
SAST ✅ PASSED No security issues
Bugs ✅ PASSED Rating S: No bugs
IAC ✅ PASSED No IAC issues

View Full Results

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Document StrykerJS as Moderaty’s mutation runner in mutation-testing skill

📝 Documentation 🕐 Less than 5 minutes

Grey Divider

AI Description

• Add repo-specific guidance to run mutation tests with StrykerJS in Moderaty.
• Document prerequisite svelte-kit sync to avoid Vitest/rolldown tsconfig failures.
• Provide scoped/PR-scale/incremental command patterns and discipline/CI gating notes.
High-Level Assessment

The following are alternative approaches to this PR:

1. Reference AGENTS.md/tools docs instead of duplicating
  • ➕ Avoids repeating Stryker instructions across multiple docs
  • ➕ Reduces drift risk if commands/prereqs change
  • ➖ Skill doc becomes less self-contained for agents following SKILL.md only
  • ➖ Requires extra navigation/context switching during runs
2. Add a short pointer + canonical command snippets only
  • ➕ Keeps SKILL.md focused while still enabling correct first run
  • ➕ Smaller surface area to keep current
  • ➖ May omit important failure mode details (e.g., .svelte-kit/tsconfig.json prerequisite) that prevent successful execution

Recommendation: Current approach is reasonable because the mutation-testing skill is an execution guide and benefits from being self-contained with repo-specific prerequisites and safe-operating reminders. If drift becomes a concern, consider tightening it to minimal snippets plus links, but keep the svelte-kit sync prerequisite and the explicit-scope guidance in SKILL.md.

Files changed (1) +11 / -0

Documentation (1) +11 / -0
SKILL.mdAdd Moderaty-specific StrykerJS mutation-testing runbook +11/-0

Add Moderaty-specific StrykerJS mutation-testing runbook

• Introduces a new section documenting StrykerJS as the required mutation-testing tool for this repo. Adds prerequisite setup ('npx svelte-kit sync'), common scoped/PR-scale/incremental commands, and reminders about verifying survivors and treating CI threshold ratcheting as a separate maintainer-approved step.

.agents/skills-src/mutation-testing/SKILL.md

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

To customize comments, go to the Qodo configuration screen, or learn more in the docs.

Qodo Logo

@Bonobo791

Copy link
Copy Markdown
Owner Author

Review triage — no actionable findings

@qodo-code-review — 0 bugs / 0 rule violations / 0 requirement gaps. Nothing to fix.
@codacy-production — up to standards, 0 issues. Nothing to fix.
@CodeAnt-AI — quality gate PASSED; sequence diagram and review-status comments noted, informational.
@sonarqubecloud — quality gate passed.
@coderabbitai — rate-limited this run; no comments to triage. Noted.
@netlify — deploy preview ready; informational.

Docs-only change (skill SKILL.md); holding for human review.

@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Tip

For best results, initiate chat on the files or code changes.

@Bonobo791 Acknowledged. The reported checks have no actionable findings. The change is documentation-only and remains ready for human review.

You are interacting with an AI system.

@codeant-ai

codeant-ai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Question: ## review triage — no actionable findings

@qodo-code-review — 0 bugs / 0 rule violations / 0 requirement gaps. nothing to fix.
@codacy-production — up to standards, 0 issues. nothing to fix.
**** — quality gate passed; sequence diagram and review-status comments noted, informational.
@sonarqubecloud — quality gate passed.
@coderabbitai — rate-limited this run; no comments to triage. noted.
@netlify — deploy preview ready; informational.

docs-only change (skill skill.md); holding for human review.

Answer:
No actionable findings.

The added section correctly documents the repository-specific StrykerJS workflow:

  • Identifies the installed Core/Vitest runner setup and root configuration.
  • Calls out the required npx svelte-kit sync prerequisite for fresh checkouts/worktrees.
  • Provides scoped, PR-scale, and incremental commands.
  • Reinforces manual survivor verification.
  • Keeps CI threshold ratcheting as a separate maintainer-approved decision.

The change is documentation-only, focused, and consistent with the stated requirements.

@qodo-code-review

Copy link
Copy Markdown

Review triage — no actionable findings

@qodo-code-review — 0 bugs / 0 rule violations / 0 requirement gaps. Nothing to fix.
@codacy-production — up to standards, 0 issues. Nothing to fix.
@CodeAnt-AI — quality gate PASSED; sequence diagram and review-status comments noted, informational.
@sonarqubecloud — quality gate passed.
@coderabbitai — rate-limited this run; no comments to triage. Noted.
@netlify — deploy preview ready; informational.

Docs-only change (skill SKILL.md); holding for human review.

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.

@Bonobo791
Bonobo791 merged commit 1e2ece7 into main Aug 5, 2026
18 of 21 checks passed
@Bonobo791
Bonobo791 deleted the docs-skill-stryker branch August 5, 2026 14:24
@Bonobo791

Copy link
Copy Markdown
Owner Author

Triage closed

@CodeAnt-AI, @qodo-code-review, @coderabbitai — thanks for confirming no actionable findings. Docs-only; holding for human review.

@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Tip

For best results, initiate chat on the files or code changes.

@Bonobo791 Acknowledged. Review triage is closed. The documentation-only change remains ready for human review.

🐇

You are interacting with an AI system.

@codeant-ai

codeant-ai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Question: ## triage closed

****, @qodo-code-review, @coderabbitai — thanks for confirming no actionable findings. docs-only; holding for human review.

Answer:
No actionable findings. The documentation addition is clear and appropriately scoped:

  • Establishes StrykerJS as the repository-standard mutation runner.
  • Documents the required svelte-kit sync prerequisite and explains the resulting failure mode.
  • Provides scoped, PR-scale, and incremental commands.
  • Correctly separates survivor review from CI threshold ratcheting.
  • Does not modify code paths or introduce configuration changes.

The change is suitable for human review.

@qodo-code-review

Copy link
Copy Markdown

Triage closed

@CodeAnt-AI, @qodo-code-review, @coderabbitai — thanks for confirming no actionable findings. Docs-only; holding for human review.

Acknowledged—no actionable findings from my review. The documentation-only change is ready for human review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed size:S This PR changes 10-29 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant