contributing

Plugin contributing from marketplace luisburgos in luisburgos/skills. Commands read from the repo's manifest — 1 month ago.

Skills (20)

• drafting-release-notes

  Draft curated GitHub Release notes for an existing tag — themed sections, PR and commit references, a collapsible full commit list, a compare link — as a draft the user approves before it goes public. Use when the user wants to cut a GitHub release, write notes for a tag or version, publish a releas

• generating-changelogs

  Generate a release's CHANGELOG.md entry from Conventional Commits with conventional-changelog, in the version bump, or set a repository up to do so. Use when bumping a version or a build number, adding a changelog to a repository, "update the changelog", "generate the changelog", backfilling entries

• writing-adrs

  Write or review an architecture decision record, and check first that the decision needs one. Use when recording a decision, writing or reviewing an ADR, or before creating a file where the repository keeps its decision records, often docs/adr/. Also use when a repository has no decision records yet

• writing-prds

  Draft, fill in or review a product requirements document: what a part of the product does, its flows, edge cases and acceptance criteria. Use when writing a PRD, starting a new effort, "draft a spec", reverse-engineering a PRD from something already built, or before creating a file where the reposit

• writing-pull-requests

  Write or rewrite a pull request description, and check first that the change is one pull request rather than several. Use when opening a pull request, filling in a pull request template, splitting a change into pull requests, or reviewing a description before it goes out. Also use when a repository

• drafting-store-notes

  Draft the store copy for a mobile release: the Google Play release notes (en-US and es-419 by default, 500 characters each) and the TestFlight "What to Test" text, from the release's CHANGELOG.md entry, approved in conversation before any file is written. Use when "generate the store notes", "draft

• assessing-cycle-goals

  Measure a cycle against the goals it started with, score the estimates that were made, and close the cycle by appending to history.

• collecting-cycle-data

  Collect what actually happened in a cycle — git across the configured repos, plus an optional task export — into the cycle's primary record.

• configuring-cycle-tracking

  One-time setup for cycle tracking — writes the config and an empty history so the first cycle can begin.

• naming-skills

  Name a new skill, or audit existing skill names against this repo's taxonomy. Use when choosing what to call a skill or renaming one, or when checking a tree of skills for naming drift. Also use when another skill needs the taxonomy to justify a name it is producing.

• reaim

  Set the coming cycle's goals — draft 3 to 5 goals with theory and practice confidence estimates, carry or drop what did not land, and force a decision on anything unlikely to actually happen. A thin facade over setting-cycle-goals.

• recap

  Close out a finished cycle's record — collect what happened into the primary record, then optionally write the readable review. A thin facade over collecting-cycle-data and writing-cycle-review.

• recheck

  Close a finished cycle against the goals it started with — judge each goal, score the estimates, write the assessment, and freeze the cycle into history. A thin facade over assessing-cycle-goals.

• reviewing-cycle-trends

  Read across many cycles for the patterns a single cycle cannot show — carried goals, estimate calibration, and gaps in the record.

• setting-cycle-goals

  Draft the next cycle's goals, each with the plan that would produce it and theory and practice confidence estimates of that plan, and force a decision on any goal you are unlikely to actually do.

• weekly-cycle-model

  The shared model of the weekly cycle — the sequence, the artifact contract, and the rules every cycle skill obeys. Read before running any of them.

• writing-cycle-review

  Write the readable narrative of a cycle — charts and prose over the collected data, for the person who lived it.

• auditing-ui-blueprint-implementations

  Audit an existing component or page implementation against its blueprint, and report each gap with where its fix starts.

• deriving-component-blueprints

  Derive a stack-agnostic component blueprint from a mockup or from existing code.

• deriving-ui-page-blueprints

  Derive a stack-agnostic page blueprint from a mockup, naming the components it is built from and the data it shows them.

Similar plugins