Scylla

Run section orchestrators to coordinate multi-component workflows. Use when starting work on a section.

Validate agent YAML frontmatter and configuration. Use before committing agent changes or in CI.

Reply to PR review comments using the correct GitHub API endpoint. Use when responding to inline code review feedback (not gh pr comment).

Run Mojo tests using mojo test command. Use when executing tests or verifying test coverage.

Track implementation progress against plan. Use to monitor component delivery and identify blockers.

Check agent configuration coverage across hierarchy levels and phases. Use to ensure complete agent system coverage.

Generate visual hierarchy diagrams of agent system showing levels and delegation. Use for documentation or onboarding.

Test agent delegation patterns to verify hierarchy and escalation paths. Use after modifying agent structure.

Parse and analyze CI failure logs to identify root causes and error patterns. Use when CI builds fail to understand what broke.

Analyze SIMD usage opportunities in Mojo code. Use to find performance optimization opportunities.

Run local builds with proper environment setup. Use when building code locally to verify changes before pushing.

Check Mojo code for memory safety issues (ownership violations, use-after-free, etc.). Use to catch memory bugs.

Generate review checklists for different change types. Use to customize review focus based on what was changed.

Generate Architecture Decision Records (ADRs) to document significant architectural decisions. Use when making important technical decisions that need documentation.

Post structured documentation to GitHub issue as a comment. Use when starting work on an issue to document approach and track progress.

Update development blog with implementation milestones, learnings, and progress. Use after completing major milestones or phases.

Validate markdown files for formatting, links, and style compliance using markdownlint. Use before committing documentation changes.

Extract and summarize test failures from logs. Use to quickly understand what tests failed and why.

Diagnose and fix CI/CD failures by analyzing logs, reproducing locally, and applying fixes. Use when CI checks fail on pull requests.

Generate fix suggestions based on error patterns and best practices. Use when analyzing failures to get actionable remediation steps.

Batch merge multiple PRs by label (e.g., all 'ready-to-merge' PRs). Use when you have multiple approved PRs to merge.

Check CI/CD status of a pull request including workflow runs and test results. Use when verifying if PR checks are passing or investigating CI failures.

Create a pull request properly linked to a GitHub issue using gh pr create --issue. Use when creating a PR that implements or addresses a specific issue.

Address PR review feedback by making changes and replying to comments. Use when a PR has open review comments needing responses.

Retrieve all review comments from a pull request using the GitHub API. Use when you need to see what feedback has been provided on a PR.

End-to-end implementation workflow for a GitHub issue from planning through PR creation. Use when starting work on an issue from scratch.

Post structured updates to GitHub issues. Use to report progress, findings, and implementation notes directly to issues.

Read context from GitHub issue including body and comments. Use before starting implementation work or when prior context is needed.

Comprehensively review a pull request including code changes, CI status, and adherence to project standards. Use when asked to review a PR.

Create GitHub Actions workflows for automated package building and distribution. Use in package phase to automate .mojopkg building and release creation.

Build Mojo packages (.mojopkg files) for distribution. Use when creating distributable libraries or during packaging phase.

Format Mojo code using mojo format command. Use when preparing code for commit or when formatting checks fail.

Validate Mojo syntax against current v0.26.1+ standards. Use to catch syntax errors before compilation.

Verify memory safety in Mojo code including ownership, borrowing, and lifetime management. Use when reviewing code or debugging memory issues.

Apply SIMD optimizations to Mojo code for parallel computation. Use when optimizing performance-critical tensor and array operations.

Validate type safety in Mojo code including parametric types and trait constraints. Use during code review or when type errors occur.

Refactor and finalize code after parallel phases complete, addressing technical debt. Use in cleanup phase to polish code before merge.

Coordinate implementation phase by delegating tasks and ensuring code quality. Use during implementation phase to manage engineer tasks.

Create distributable packages including .mojopkg files and archives. Use during package phase to prepare components for distribution.

Generate comprehensive plan documentation following Template 1 format. Use when creating plan.md files for new components or subsections.