Stage
Official@reviewstage
Offers technical oversight for Git-based development, managing pull request resolution, design system consistency, and repository quality standards.
Agent Skills by Stage
Showing 9 vetted skills indexed across 1 GitHub repositories.
linear-issue
Create a Linear issue from current coding context and git branch.
rebase-origin-main
Rebase the current Git branch onto origin/main and resolve conflicts iteratively.
trade-off
Identify deliberate trade-offs to prevent scope creep during planning and reviews.
fixing-pr-comments
Triage unresolved GitHub PR review threads and apply fixes via GraphQL.
deslop-ui
Enforce spacing, typography, color, and layout rules for UI design systems.
quality-review
Evaluate code changes against AGENTS.md quality criteria and generate a consolidated report.
iterate-pr
Monitor open pull requests and apply fixes for review comments, CI failures, and merge conflicts.
fixing-ci
Diagnose and fix GitHub CI failures through atomic commits and local verification.
stage-chapters
Generate narrative Stage chapters from git branch diffs for browser review.
Frequently Asked Questions About Stage
FAQPage SchemaWhat specific development tasks does Stage enable?βΌ
Stage enables developers to manage pull request lifecycles, resolve merge conflicts, enforce UI design system constraints, and track project issues. It facilitates the triage of GitHub review threads, fixes continuous integration failures, and generates narrative documentation from branch diffs to streamline code reviews.
Which engineering personas benefit from these capabilities?βΌ
Software engineers, frontend developers, and technical leads benefit from these capabilities. The functionality is designed for teams managing high-velocity repositories who require consistent code quality, strict adherence to UI design system rules, and efficient resolution of pull request feedback loops.
What are the prerequisites for implementing these capabilities?βΌ
Implementation requires an active GitHub repository and a configured Linear workspace for issue tracking. Users must have appropriate repository permissions to execute GraphQL operations for pull request management and local environment access to perform Git rebase operations and verify continuous integration fixes.