Yusuf Başpınar
Community@ybaspinar · Eskişehir
Yusuf Başpınar publishes 16 engineering-discipline skills covering the full software lifecycle: planning, implementation, code review, verification, operations, incident response, and TypeScript standards.
Agent Skills by Yusuf Başpınar
Showing 16 vetted skills indexed across 1 GitHub repositories.
structural-implementing
Implements code paths with input parsing, idempotency, resource bounds, and failure visibility checks.
structural-reviewing
Reviews code changes, migrations, and operational diffs for structural risks like silent failures and unbounded growth.
structural-operating
Review releases, rollouts, and runbooks for reversible deployment and safe production operation.
structural-investigating
Diagnose defects and unknowns through time-boxed, hypothesis-driven investigation workflows.
structural-triage
Triage tickets, bug reports, and incidents by evidence and blast radius.
structural-planning
Converts fuzzy requirements and migrations into executable engineering plans with defined acceptance criteria.
conventional-impact
Convert completed engineering work into evidence-backed impact summaries and manager updates.
structural-verifying
Verifies fixes, features, and migrations against running-system behavior with red-before-green proof.
objective-code-review
Review commits, pull requests, and merge requests for requirement correctness and structural defects.
structural-retrospective
Converts incidents and postmortems into reproducible evidence, system-gap analysis, and owned follow-up issues.
structural-integrating
Reviews integration of features, services, and dependencies into larger systems for boundary and failure risks.
structural-correctness
Review software designs and changes for boundary, invariant, and failure-mode correctness.
fault-tolerant-design
Reviews software designs for isolation, redundancy, static stability, and progressive delivery under failure.
structural-retirement
Guides safe deprecation and deletion of APIs, features, services, tables, and code paths.
typescript-coding-standards
Reviews and guides TypeScript code toward typed errors, boundary parsing, and safe domain modeling.
deliberate-response-loop
Converts emotional pressure and avoidance into clear perception, deliberate choice, and concrete next actions.
Frequently Asked Questions About Yusuf Başpınar
FAQPage SchemaWhat tasks can I accomplish with ybaspinar's skills?▼
The 16 skills cover the full software lifecycle: planning fuzzy requirements into executable plans, implementing endpoints and migrations, reviewing PRs and MRs, verifying fixes in running systems, operating releases with rollbacks, triaging tickets, investigating defects, retiring deprecated code, and enforcing TypeScript coding standards.
Who should use these engineering skills?▼
Software engineers, tech leads, and engineering managers handling code reviews, incident response, sprint delivery, and reliability work. The conventional-impact skill also suits developers preparing MR descriptions, sprint review notes, manager updates, release notes, and performance-review bullets from code changes.
How do the skills handle production reliability and failures?▼
The fault-tolerant-design skill addresses critical paths, queues, database changes, failover, and failure modes. Structural-operating covers shipping, monitoring, rollbacks, and runbooks, while structural-investigating and structural-retrospective handle debugging, incident diagnosis, postmortems, and follow-up work.
Do the skills support TypeScript development specifically?▼
Yes. The typescript-coding-standards skill governs writing, reviewing, and refactoring TypeScript with focus on typed errors, parsing boundaries, domain types, module boundaries, tests, adapters, configuration, and telemetry conventions.
What prerequisites are needed to use these skills?▼
No external dependencies, licenses, or runtime requirements are stated in the manifest. The skills are instruction-based engineering discipline guides invoked contextually—each description specifies when to apply it, such as during code review, incident triage, migration planning, or deprecation work.