engineering

Plugin engineering from marketplace yasik-skills in yasik/skills. Commands read from the repo's manifest — 7 days ago.

Skills (14)

• babysit-pr

  Monitor a named open GitHub PR, address valid review findings and CI failures, and continue until current-head merge readiness or a genuine stop. Use for an ongoing watch, not a one-shot review.

• coding-style

  Apply Andrii's Python and TypeScript coding standards when implementing, simplifying, or reviewing code, APIs, packages, and tests. Use for explicit types, module boundaries, public exports, readable control flow, and useful comments.

• create-pr

  Prepare and open or update a reviewable GitHub pull request using the bundled editable template. Use when asked to create a PR or prepare its title/body; preserve draft-only and no-push requests.

• debug

  Diagnose and fix a concrete bug or failing check by tracing the actual failure and validating the smallest root-cause correction. Use for broken behavior, regressions, and CI failures rather than speculative cleanup.

• design

  Resolve a consequential engineering design choice into the smallest useful contract and reviewable implementation plan. Use for architecture, new abstractions, migrations, or a request to plan before coding.

• dev-docs

  Write, edit, or review developer documentation using source-verified facts and concise technical prose. Use for READMEs, API references, guides, release notes, and substantive documentation style questions.

• develop

  Carry a concrete engineering task through design, implementation, verification, review, and delivery within its authorized scope. Use for end-to-end feature or fix work; route isolated reviews and research to their own skills.

• docs-portal

  Discover and run the repository's documentation build and checks after docs-sync or edits to public documentation, navigation, or portal rendering.

• docs-sync

  Audit or update public documentation against current code, covering changed behavior, defaults, examples, and navigation. Use for documentation coverage or as the documentation stage of authorized implementation work.

• optimize

  Improve measured performance, cost, or resource use while protecting output quality. Use for a named workload or trace with a baseline; do not claim optimization from code appearance alone.

• release

  Cut a versioned release: choose the version, update version files and the changelog, verify, commit, tag, and publish within explicit authority, then confirm the published artifacts. Use when asked to make, cut, or publish a release or tag.

• review-code

  Review a specific diff or PR for correctness, scope, architecture, security, tests, and repository standards. Report findings by default; apply validated findings only when the request authorizes fixes.

• simplify-code

  Simplify settled code in a named diff or recent change for reuse, readability, and efficiency while preserving behavior. Use after implementation and before final review; not for a broad redesign or bug fix.

• unit-test-coverage

  Select, write, and review meaningful tests of public functions and interfaces. Use when adding behavior, fixing a regression, reviewing test quality, or diagnosing failing tests. Every test must protect a critical behavior or flow; never add tests only to increase coverage.

Similar plugins