GS Personal
Official@gs-personal
Offers engineering oversight, quality assurance, and release management capabilities for software development lifecycles.
Agent Skills by GS Personal
Showing 9 vetted skills indexed across 1 GitHub repositories.
GS-Personalgstack-upgrade
Upgrades gstack to latest version and summarizes what's new from CHANGELOG.md.
GS-Personalqa
Automate web application QA testing across four modes and generate structured health reports.
GS-Personalsetup-browser-cookies
Import authenticated browser cookies into Playwright sessions for QA testing.
GS-Personalreview
Identify safety and quality issues in code diffs against main.
GS-Personalplan-ceo-review
Enforce a structured, risk-aware review workflow for feature plans.
GS-Personalretro
Analyze weekly git data to compute per-author metrics and session patterns.
GS-Personalbrowse
Automate end-to-end browser interactions for QA testing and agent workflows.
GS-Personalship
Automate feature branch merges, tests, version bumps, changelog updates, and PR creation.
GS-Personalplan-eng-review
Evaluate engineering implementation plans for architecture, data flow, edge cases, and test coverage.
Frequently Asked Questions About GS Personal
FAQPage SchemaWhat specific tasks can GS Personal perform for engineering teams?▼
GS Personal enables end-to-end browser testing, automated release management, and structured code review. It facilitates version upgrades, changelog generation, PR merging, and the analysis of git-based author metrics to ensure consistent software quality and delivery standards.
Which personas benefit most from these capabilities?▼
Software engineers, QA testers, and engineering managers benefit from these capabilities. The suite is designed for technical teams requiring rigorous code review enforcement, automated testing of web interfaces, and data-driven insights into development velocity and release health.
What are the prerequisites for running these testing and review functions?▼
Execution requires a configured git environment and access to browser-based session cookies for testing modules. Users must maintain standard repository structures, including CHANGELOG.md files and feature branches, to support the automated merging, versioning, and review processes provided by the registry.