Skip to content
cccskills
FreePublished on GitHub

vibe-pr

How to write a Vibe pull request title and description — simple, clear English that says what the change does, its benefit, and why, with pros and cons, charted results, and screenshots where they apply. Use when opening a pull request, or writing or rewriting a PR title or description.

The English summary is being prepared. Showing the original description.

cmicali/vibe
Works withGitHub

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Writing a pull request

Write the description in simple, clear English that someone outside the code can follow. Say plainly:

  1. What it does: the change, in a sentence or two.
  2. The benefit: what is better for the user or the codebase.
  3. Why: the problem it solves, or the reason this approach was chosen.

Then, only where they apply:

  • Pros and cons: a short list, when the change is a trade-off or there was a real alternative.

  • Results: for performance, quality, or size work, show the numbers clearly and simply: a small before/after table, plus a chart. GitHub renders Mermaid, so a bar chart can go straight into the description:

    ```mermaid
xychart-beta
    title "Track open time (ms, lower is better)"
    x-axis ["Before", "After"]
    y-axis "ms" 0 --> 120
    bar [104, 38]
```

    Label the units and say which direction is better. Name what was measured and how (the benchmark or make target), in one line.

  • Screenshots: for a new feature that can be seen, add screenshots of it in the running app, captured with the vibe-debug skill. Upload them with --attach. It works on gh pr create, gh pr edit and gh pr comment. Alt text follows the path after #. Repeat the flag for more files, up to 50. A ![alt](./after.png) reference in the body is rewritten to the uploaded file. A file the body does not reference is appended at the end. So write the body with the references where the images belong, then pass each file:

    gh pr create --title "..." --body-file pr.md --attach './before.png#Before' --attach './after.png#After'

    To add or replace pictures on a PR that already exists, edit its description with gh pr edit <n> --body-file pr.md --attach './a.png#alt'. Do not post a comment for this. A comment is a new post on a public thread, and AGENTS.md says to ask before one.

Keep it short. Leave out file-by-file narration, internal jargon, and anything the diff already shows. A reviewer should be able to read the description and know what changed, why it matters, and what it costs.

The title follows the repo's existing style: area: What it does, in the imperative (see git log --oneline).

Never name or credit the AI agent or tool that helped write the change (AGENTS.md, "No agent attribution").

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

vibe-audio-quality

Free

Check and document Vibe's audio quality and conformance. Runs public conformance and torture corpora (IETF CELLAR FLAC files, ISO/IEC 14496-26 Layer III, FFmpeg FATE samples, McGill WAVE and AIFF samples, EBU BW64 tests, Chromium and Firefox media tests, TagLib test data) through the real decoders. Valid files must match their FLAC MD5 or reference decode within the ISO accuracy limits, decode to the length the handle states and seek exactly. Every file must finish with finite samples. Also regenerates docs/audio-quality.md's charts and its corpus results matrix. Use after changing a decoder, a parser, the file-open path or the resampler, before a release, when asked whether decoding is correct or conformant, or to update the audio quality page.

The English summary is being prepared. Showing the original description.

cmicali/vibe49Updated Oct 24, 2026

vibe-debug

Free

Launch, drive, inspect, and visually verify the Vibe app — macOS, and the iOS simulator loop (launch-ios.sh, the debug-ios.sh command channel, the drive-ios.sh touch driver for taps and drags, silent flags, screenshots, host-side log streaming). Use whenever a change needs end-to-end verification, a screenshot of the running app, playback/UI state inspection, or appearance (light/dark) testing.

The English summary is being prepared. Showing the original description.

cmicali/vibe49Updated Oct 24, 2026

vibe-perf

Free

Measure Vibe's performance and compare two versions of the code. VibeBenchComponents drives the production decode, open, seek, resample, pitch, waveform, tempo/key, meter, metadata and cache code in-process with no app, counting retired instructions as well as wall and CPU time; perf.py builds it at any git ref and runs two refs interleaved (make bench-components); profile.sh finds one benchmark's hotspots; --analyze proves an analyzer change exact. Also owns the performance page (docs/performance.md): component charts per release (make bench-components-releases), app benchmarks (make bench-app), both (make bench-releases), redraw (make bench-report). Use before and after any change that could move cost, to find where time goes, to choose between implementations, to back a performance claim with numbers, or when asked to update, rerun or regenerate the performance page for a release, pre-release or new machine.

The English summary is being prepared. Showing the original description.

cmicali/vibe49Updated Oct 24, 2026

vibe-release

Free

Build, sign, notarize, and ship Vibe on both platforms — the macOS Developer ID (make release) and App Store (make appstore-build) paths, the iOS App Store path (make appstore-build-ios), the GitHub release publish (make github-release), the Homebrew tap bump (make brew-set-version), the localized product-page metadata upload (make appstore-upload-metadata), the shared App Store Connect API key and its Admin-role requirement, and the signing traps each script preflights. Use when cutting a release, distributing a build, shipping or TestFlighting the iOS app, updating App Store copy or screenshots, or debugging a signing/notarization/upload failure.

The English summary is being prepared. Showing the original description.

cmicali/vibe49Updated Oct 24, 2026

vibe-stress

Free

Stress, soak, fuzz, and torture the running Vibe app against a folder of real audio files — seeded random controller actions without pointer input, with consistency, leak, hang, and crash oracles, a single-playlist skip/seek torture suite for the delivery races that only open when transport outruns the metadata scan, a deterministic cloud-loading scenario suite over a fake file provider (download ordering, the foreground hold, the open deadline), plus the sanitizer (ASan/UBSan/TSan) and malloc-debug build matrix. Use for soak or endurance runs, memory-leak and resource-growth hunting, race hunting, fuzzing the file-loading path, hammering skips and seeks on a large playlist, testing cloud/placeholder loading order, or minimizing a failing run to a repro.

The English summary is being prepared. Showing the original description.

cmicali/vibe49Updated Oct 24, 2026

vibe-strings

Free

The localization pipeline — VibeStrings.h registry conventions, the extract-strings.sh preprocessor pass and extractionState rules, catalog and InfoPlist.xcstrings mechanics, authoring translations and the untranslated-keys release gate, translation terminology and per-language conventions, the pseudolocale audit, and the localized App Store product page. Use when adding or rewording any user-facing string, translating catalog keys, editing VibeStrings.h or the .xcstrings catalogs, debugging make strings / make check-strings, testing a language, or updating App Store copy or screenshots.

The English summary is being prepared. Showing the original description.

cmicali/vibe49Updated Oct 24, 2026

See all skills by cmicali

Report a problem with this skill