Gus Gadirov
Community@gusgad · Berlin, Germany
Gus Gadirov publishes engineering-discipline skills covering code review, TDD, systematic debugging, browser-based UI verification, and durable knowledge capture for software teams.
Agent Skills by Gus Gadirov
Showing 9 vetted skills indexed across 1 GitHub repositories.
gusgadcode-review
Guides requesting code reviews and responding to feedback with technical verification.
gusgadagent-skills
Guides authoring and maintaining discoverable SKILL.md skill files for AI agents.
gusgadplaywright
Write and run purpose-built Playwright scripts to verify Angular UI behavior in a real browser.
gusgadralph-wiggum
Automates iterative agent loops that grind tasks until verification commands pass.
gusgadcompound-engineering
Documents non-obvious bug fixes and engineering decisions as searchable markdown files in docs/solutions.
gusgadtest-driven-development
Enforces red-green-refactor test-first workflow for features and bugfixes.
gusgadsystematic-debugging
Diagnose bugs through root cause investigation before proposing fixes.
gusgadbrainstorming
Refines ideas into approved designs through structured dialogue before implementation begins.
gusgadverification-before-completion
Enforces running fresh verification commands before claiming work is complete.
Frequently Asked Questions About Gus Gadirov
FAQPage SchemaWhat tasks can I accomplish using Gus Gadirov's skills?▼
You can structure code reviews, apply test-driven development before writing implementation code, debug failures systematically, verify UI behavior end-to-end with Playwright, brainstorm requirements before building, run unattended iteration on verifiable tasks, and document non-obvious decisions for reuse.
Who are these skills designed for?▼
Software engineers and technical leads who want disciplined development practices: reviewers handling PR feedback, developers writing features or bugfixes test-first, and teams validating client UI behavior in a real browser rather than relying only on unit tests.
How do the skills fit into a development session?▼
Each skill triggers at a specific phase: brainstorming before ambiguous work, TDD before implementation, systematic-debugging when failures appear, verification-before-completion before committing, code-review before merging, and compound-engineering afterward to preserve what was learned.
What prerequisites do these skills require?▼
Skills are stored under .agents/skills/ with a SKILL.md file containing a name and description field. The playwright skill requires a browser-driven test setup; ralph-wiggum requires an automatic success signal such as tests, a linter, or a build command.
How do I create a new skill for this registry?▼
Use the agent-skills skill: it covers SKILL.md structure, writing an effective description field, deciding whether a technique deserves to become a skill, and keeping the skill discoverable and token-efficient within the .agents/skills/ directory.