farmostwood avatar

farmostwood

Community

@psyche911 · Sydeney

23Followers
|
76Public Repos
|
9Published Skills

The world has kissed my soul with its pain, asking for its return in code.

Skills Distribution
DomainDeveloper To...Web QA & Browser T.. (40%)Code Review & Diff.. (20%)Git Release & Vers.. (15%)Engineering Plan C.. (15%)

Agent Skills by farmostwood

Showing 9 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About farmostwood

FAQPage Schema
What tasks can I accomplish with farmostwood's skills?▼

You can drive a headless browser at ~100ms per command to test features and dogfood user flows, run structured QA with health scores, review PR diffs for SQL and trust boundary issues, critique plans in CEO or engineering-manager modes, generate commit-based retrospectives, and ship releases from merge to PR creation.

Who are these skills designed for?▼

They target software engineers, QA testers, engineering managers, and founders. The review and plan-critique skills serve leads validating architecture and scope, while gstack, browse, and qa serve developers verifying deployments, responsive layouts, forms, and uploads with annotated screenshot evidence.

How do the QA and browser testing skills work in practice?▼

Invoke qa for full, 30-second smoke, or regression testing against a baseline; it outputs a structured report with health score and repro steps. Use gstack or browse to navigate URLs, interact with elements, diff before/after states, and capture annotated screenshots. Run setup-browser-cookies first for authenticated pages.

What permissions and dependencies do these skills require?▼

Skills declare allowed-tools frontmatter: Bash and Read for browser skills; Write, Edit, Grep, Glob, and AskUserQuestion for review, ship, and plan skills. They rely on an installed Chromium-family browser for cookie import and a Git repository with commit history for retro and ship.

How does the ship skill handle releases?▼

Ship executes the full release sequence: merge main, run tests, review the diff, bump VERSION, update CHANGELOG, commit, push, and create the pull request. It uses Bash, Read, Write, Edit, Grep, Glob, and AskUserQuestion to confirm steps interactively during the release.