steward

Plugin steward from marketplace gustavovalverde-skills in gustavovalverde/skills. Commands read from the repo's manifest — today.

Skills (13)

• advisory-triage

  Handle security vulnerability reports and GitHub security advisories for a repository, from intake and duplicate screening through contract assessment, CVSS scoring, fix review, release planning, advisory drafting, and disclosure readiness. Use when a vulnerability report or draft advisory arrives,

• backlog-triage

  Triage GitHub issues and pull requests, including validity, duplicates, competing implementations, canonical issues, and native organization such as issue types, sub-issues, and blocking links. Use when assessing a backlog batch or area, continuing earlier triage, checking whether a single issue or

• change-implementation

  Implement an issue, feature, or non-trivial bug fix in an existing codebase as one complete change, from the request and its discussion through code, tests, and documentation, including breaking changes when the repository allows them. Use when asked to implement, fix, or build something whose chang

• codebase-structure

  Decide where code belongs, including file and module placement, splitting or merging modules, flattening or nesting directories, and moving files across boundaries. Use when the user asks where something should go, whether to split or merge files, how to organize a folder or package, or to move code

• docs-writing

  Write or restructure documentation such as tutorials, how-to guides, READMEs, reference pages, conceptual explanations, proposals, RFCs, and ADRs, plus explanatory text for slides and diagrams. Use when creating or substantially revising documentation that readers learn from, follow, look up, or dec

• identifier-naming

  Choose or review names for variables, functions, types, files, folders, and domain vocabulary, and carry out renames. Use when the user asks what to call something, whether a name is clear or misleading, or to rename a symbol, key, file, or folder without moving it. Not for deciding where code belon

• pr-writing

  Write or revise pull request titles and descriptions, commit messages, changesets, changelog entries, and release notes. Use when opening or updating a pull request, describing a diff or a stacked change for reviewers, or summarizing a change for users, even in a single sentence. Not for design docu

• prior-art-research

  Research prior art for an engineering decision, meaning how specifications, open-source implementations, libraries, and real clients handle a protocol behavior, security property, default, or API shape, with each claim ranked by the strength of its evidence. Use when choosing such a behavior or defa

• public-api-design

  Design or review developer-facing contracts such as library APIs, SDKs, plugin and extension interfaces, HTTP endpoints, CLIs, configuration, generated clients, and tools that agents call, such as MCP servers. Use when adding or changing a public surface, judging whether an API is easy to use correc

• software-design

  Plan a feature or substantial refactor, or assess a design's interfaces, state ownership, module boundaries, abstractions, and error handling. Use when implementation needs decisions that are still open, when the user asks how to approach or structure a change, how an internal module should expose i

• text-editing

  Review or revise an existing draft for clarity, organization, readability, and audience fit, such as emails, announcements, essays, reports, or documentation passages. Use whenever the user shares prose and asks to edit, tighten, simplify, or get feedback on it, even a single paragraph or section. N

• ui-composition

  Compose product screens, components, forms, tables, navigation, and landing or pricing sections from the existing design system with the fewest elements that let the user act. Use when building or changing a screen or flow, including small tweaks, and before adding a button, badge, card, filter, ban

• ui-copy

  Write or review interface text such as labels, buttons, headings, field hints, empty states, errors, confirmations, tooltips, and onboarding messages. Use when building or changing a screen, component, or flow that shows text to users, even for a single label or message, and even when the request is

Similar plugins