Ingénierie & IT
Skills Gemini Enterprise : ingénierie & it.
المهارات 12
- مهارة
Architecture decision record
Writes an Architecture Decision Record in Nygard or MADR format: context and forces, decision drivers, options considered with honest pros and cons, the decision and its rationale, positive and negative consequences, reversibility and a revisit trigger, and links to the decisions it supersedes.
- مهارة
Backlog grooming
Grooms a Jira backlog before refinement: finds duplicates, stale and zombie tickets, vague stories without acceptance criteria, oversized items to split, missing dependencies and bugs without severity, scores each item against INVEST and a Definition of Ready, and produces a refinement agenda with sizing questions and proposed edits.
- مهارة
Bug report writer
Turns a vague problem report, Slack thread, support ticket, screenshot description or log excerpt into a Jira-ready bug report: clear title, reproducible steps, expected versus actual, environment, impact, severity separated from priority, evidence links, a duplicate check and open questions.
- مهارة
Code explainer
Explains a code file, function, pull request or area of a GitHub repository for a newcomer, a non-developer or a reviewer: what it does in plain words, where it sits in the system, the main flow step by step with file and line references, key concepts and jargon, data in and out, side effects and dependencies, gotchas, and where to start reading or changing it. Adapts depth to the audience.
- مهارة
Engineering standup summary
Builds an engineering team standup summary from real activity in Jira and GitHub (plus Slack or Chat): per person or per work item, what moved since the last standup, what is planned today, blockers and items waiting on someone, PRs waiting for review, aging work in progress, and risks to the sprint goal. Async-ready for posting or as a one-screen board for the live standup.
- مهارة
Incident postmortem
Writes a blameless SRE-style incident postmortem from the incident channel, tickets, alerts and meeting notes: summary, customer and business impact, SLO and error budget consumed, minute-by-minute timeline with detection and mitigation times, root cause through 5 whys, contributing factors, what went well, where we got lucky, and prioritized action items with owners.
- مهارة
Incident status update
Drafts incident status updates during an ongoing outage or degradation, in three versions from the same facts: technical update for the incident channel, plain-language update for business and store teams, and a customer-facing status message for approval, each with severity, impact, current status, next steps and the time of the next update, at a cadence matched to severity.
- مهارة
PR description writer
Writes a reviewer-friendly GitHub pull request description from the diff, commits and linked Jira issue: a Conventional Commits title, what changed and why, how it was tested, risks and rollback, deployment notes and a review guide that tells reviewers where to look first.
- مهارة
PR review assistant
Reviews a GitHub pull request like a staff engineer: checks the diff against the linked Jira ticket, then lists findings by severity (blocker, major, minor, nit) across correctness, security (OWASP Top 10, leaked secrets), performance, tests and readability, each with file and line, why it matters and a suggested fix, plus a verdict and ready-to-paste review comments.
- مهارة
Release readiness check
Runs a go/no-go readiness check for a release from Jira and GitHub: scope done versus planned, open blockers and critical bugs, CI and test status as reported, database migrations and backward compatibility, feature flags, rollback plan, monitoring and on-call, change freeze and peak-period risk, and stakeholder communication, ending with a Go / Go with conditions / No-go recommendation and the exact conditions.
- مهارة
Runbook writer
Writes an operational runbook for a service, alert or recurring operation: when it applies (alert names, symptoms), prerequisites and access, fast triage, diagnosis branches, numbered remediation steps each with an expected result and a verification, rollback, escalation path and communication hooks, built from code, configs, past incidents and team docs.
- مهارة
Tech spec writer
Writes a Google-style technical design document for a feature or system change: context and scope, goals and non-goals, the proposed design with APIs, data model and sequence, alternatives considered with trade-offs, cross-cutting concerns (security, privacy, reliability with SLOs, cost, observability), migration and rollout plan, and open questions for reviewers.