148 skills (repositories by garrytan) · sorted by popularity
Set up and use gstack in Capy or Claude Code for planning, code review, debugging, and release work. It checks the local environment, handles installation or repairs when needed, and selects the workflow instructions for the task.
Plan a paid evaluation with predefined success criteria, comparison groups, decoy items, and stopping rules. Rehearse without spending, then run a three-item paid pilot and use its spending table to inform approval.
Turn the most recent successful /scrape workflow into a reusable browser skill saved on disk. It builds a script, tests, and sample test data from the conversation, checks them, and asks before committing the result.
Create engineering retrospectives from Git history, covering delivered changes, work patterns, test code ratios, and frequently changed files. Review individual contributions and improvement opportunities, save metrics, and compare results with earlier periods.
Prepare code changes for sharing by merging the base branch, running tests, and reviewing the diff. Update VERSION and CHANGELOG, then commit, push, and create a pull request, a proposal to merge the changes.
Refresh gbrain's searchable code data to match the repository and update agent search guidance in CLAUDE.md. Use it to reindex a project or investigate searches that no longer find the expected code.
Retrieve the top 30 stories from the Hacker News front page as JSON, a structured data format. Each entry includes its rank, title, link, points, and comment count for reviewing stories and their engagement.
Turn a vague request into a precise specification through five phases and file it as a GitHub issue. Optionally start a Claude Code agent in a separate working directory to begin implementation.
Review a development plan before implementation by challenging its premise, comparing alternative approaches, and examining design, security, testing, and operations. Choose whether to expand, maintain, or reduce scope, then receive a summary of agreed decisions.
Audit an existing test suite to find low-value or duplicate tests and code kept solely for those tests. Receive findings for review, with changes limited to batches you explicitly approve.
Investigate software errors by tracing code, reviewing recent changes, and reproducing symptoms. Test a specific cause before making a minimal fix, then verify the result with regression tests and a structured debug report.
Explore a product or side-project idea through guided questions, challenge its assumptions, and compare implementation approaches. Produce a design document with a chosen direction and concrete next steps, adapting the discussion to business or personal goals.
Remove the directory editing boundary set by `/freeze` so work can continue across all directories without ending the session. The existing freeze hooks remain registered, and `/freeze` can be used again to restore a boundary.
Review recent development work to find code worth sharing across existing callers. Receive ranked recommendations backed by verified source locations, estimated line savings, migration steps, and risks, without changing files or running project code.
Audit code and configuration for security flaws, documenting attack paths, impact, evidence, and coverage gaps. Static review works without running the application; qualified runtime profiles add isolated reproduction and proposed repairs while keeping verification claims separate.
Import cookies from a regular Chromium browser into a headless testing session, which runs without a visible window. Choose the browser profile and domains to prepare for testing pages that require sign-in.
Turn an English description or mermaid source into a diagram with source files, an Excalidraw editing file, and SVG and PNG images. Rendering works offline, and flowcharts and sequence diagrams support editing individual shapes and arrows.
Regenerate an iOS app's debug bridge, the code connecting it to debugging tools, using current gstack templates. Update Swift support files and typed state accessors after gstack upgrades or ViewModel and property additions.
Review a UI/UX plan before implementation, score its design dimensions, and identify missing decisions. Through discussion, the skill adds concrete improvements directly to the plan so the review produces an updated plan.
Generate several AI design options, view them on a comparison board, and collect organized feedback. Use the results to explore visual directions and refine designs when a feature’s appearance is undecided or an existing interface needs improvement.
Run a project's existing type checks, code analysis, tests, unused code detection, and shell checks. Combine results into a weighted score from 0 to 10 and track code quality trends over time.
Investigate bugs in browser flows, APIs, command-line tools, background jobs, workers, and webhooks. Produce a structured report with reproduction steps and evidence or browser scores, without changing code to fix the issues.
Review and search project knowledge that gstack has collected across work sessions. Find past lessons, prune outdated entries, and export recorded knowledge when you need to revisit earlier solutions or organize what the project has learned.
Check shell commands before they run and warn about destructive actions such as file deletion, database removal, and Git history changes. Users can approve ordinary warnings, while certain catastrophic command patterns are denied.