Coding standards, frameworks, refactoring, and code review (16.9K skills)
Update a project's changelog using GitHub releases, git history, and code differences. Select changes that matter to users, match the existing format, and write concise entries for the requested release.
Review and test a pushed Factory branch before a pull or merge request is opened. Record findings against the exact tested commit, then approve the work or return it to the builder with actionable changes.
Review a pull request by first forming an independent view of the problem and design. Investigate code, history, and evidence, then deliver a clear verdict, specific change requests, and a saved record for follow-up questions.
Investigate a GitHub issue or bug report by tracing code, checking relevant history, and testing the diagnosis where needed. Receive a concise verdict, supporting evidence, a proposed fix direction, and a record for follow-up questions.
Coordinate multiple Mastra Code workers to investigate and fix GitHub issues in parallel. Keep each issue in a separate working directory, track progress in reports, review changes, and manage pull requests, reviewer feedback, and automated checks.
Build and update Mastra application interfaces using existing components from @mastra/playground-ui. Follow shared visual styles, arrange layouts with Tailwind utilities, and connect themes and stylesheets while avoiding duplicated components or unsupported appearance overrides.
Set up Herdr Kit and its Mastra Code integration, manage repository synchronization, and create or remove managed worktrees, separate working copies for review or development. The workflow checks supported operations and verifies the resulting manager state.
Review a pull request in a Factory work session by investigating its purpose, history, implementation, tests, and security. Publish verification results and a review verdict, then record the outcome on the work card.
Write, review, or refactor React code using prioritized guidance for data fetching, bundle size, rendering, component structure, testing, and type safety. Start with high-impact issues such as sequential requests and unnecessary library loading.
Reviews pull requests for bugs, error handling, code quality, and style consistency. Organizes feedback into an overview, must-fix issues with file locations, improvement suggestions, and positive notes so reviewers can distinguish urgent problems from refinements.
Review a GitLab merge request linked to a Factory work item, verify the current commit, and publish findings with a test report. It records the review verdict on the card and prepares a session handoff without merging.
Review open Mastra GitHub issues and trace reported defects to source code. Apply the @mastra/core label to confirmed core bugs, report uncertain ownership, and summarize whether fixes are active, stale, or unclaimed.
Turn pull request changes, commits, and test evidence into a self-contained HTML guide. Explain the problem, system context, before-and-after behavior, and key code changes so reviewers know where to focus.
Triage a GitHub issue by reviewing its discussion, related issues, and fixing pull requests. Publish a concise comment with classification, severity, evidence, and the next action, then update a small set of triage labels.
Query Herdr's Review Manager and Work Manager across repositories to recommend actionable pull requests. Compare review status, automated checks, size, and local state, and create local review checkouts for explicitly confirmed remote-only records.
Configure Factory board behavior and GitHub or Linear event handlers in deployment code. Adjust stage transitions, phase meanings, and tool-result handling, then check the changes with focused tests and versioned audit records.
Split a large pull request into smaller, reviewable changes. Plan branch dependencies, extract related code, verify each part, and track review changes while preserving the intent of the original work.
Draft and post GitHub pull request reviews and issue comments with precise locations, required changes, and supporting reasons. It checks the posting account, applies approval rules, and selects the appropriate review outcome.
Review code for performance bottlenecks across database queries, memory use, frontend rendering, network requests, and algorithms. Use a structured checklist to identify optimization opportunities and classify their severity according to expected load and scale.
Write, review, and refactor styles using Tailwind CSS v4 conventions. Consult guidance on CSS configuration, renamed classes, built-in styling features, and behavior changes when updating older v3 code or creating new styles.
Design instructions for agents that write, fix, review, or refactor code. Define behavior based on file access, select suitable tools, and set clear verification and completion rules for repository changes or copyable code output.
Re-review a pull request after new commits arrive. Check every previous finding, inspect the new changes for regressions, and review the full current change. Run relevant verification and publish a test report and review verdict within Factory.
Turn a Factory work item into a phased implementation plan grounded in current code and project history. Document scope, changes, tests, risks, and assumptions, then hand the plan to the execution stage.
Investigates GitHub or Linear issues through code, change history, and reproduction attempts. Produces a structured handoff covering causes, assumptions, effort, and impact, then requests the appropriate Factory workflow stage update when applicable.