SkillAgentSearch skills...

nota-pr

Open a Nota pull request the project's way — check it implements an issue a core contributor approved, branch off develop, commit in the repo's style under the contributor's own git identity, push over HTTPS, and write the description from the PR template.

Install / Use

npx skills add nota-daw/nota --skill nota-pr

Installs into whichever agent you are using.

About this skill
♊

Gemini Rules

Gemini CLI config

Quality Score

77/100

Supported Platforms

Gemini CLI

Our assessment of nota-pr

nota-pr scores 77/100 on our quality scale, 3712th of 4,698 Development & Engineering skills we index.

Its Gemini Rules is 8.3 KB long, well organised into 8 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
29/30
Structure
18/20
Description
15/15
Adoption
0/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated yesterday, so nota-pr is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-16. Automated pattern scan on 2026-11-16. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

nota-pr compared with similar skills

All 4 of these similar skills score higher than nota-pr; compare them before choosing.

SkillScoreStarsUpdatedFormat
nota-pr (this skill)by nota-daw7701d agoGemini Rules
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md

Frequently asked questions

How do I install nota-pr?
Run npx skills add nota-daw/nota. The install tabs above show the steps for each supported agent.
Which AI agents does nota-pr work with?
It is written for Gemini CLI, as a Gemini Rules file. Other agents that read the same format can often use it too.
Is nota-pr safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is nota-pr still maintained?
The repository was last updated yesterday, so nota-pr is actively maintained.

name: nota-pr description: Open a Nota pull request the project's way — check it implements an issue a core contributor approved, branch off develop, commit in the repo's style under the contributor's own git identity, push over HTTPS, and write the description from the PR template. Evidence is part of the PR, attached through the pr-assets branch: a user-visible UI change carries before/after screenshots; a performance change (engine, DSP, threading, render path, CPU/memory) carries a before/after benchmark with charts. Use whenever the user asks to open, create or prepare a PR, or to "push this for review". user-invocable: true

Opening a pull request

A Nota PR is reviewed by reading its description, so the description carries the proof: what changed, why, and what it looks like or costs before and after. Images and benchmark charts never go into develop — they live on the orphan pr-assets branch (see CONTRIBUTING.md § Images for pull requests) and are embedded by raw URL.

0. Check the approved issue

Every PR implements an issue a core contributor approved (CONTRIBUTING.md § Start with an approved issue). Before branching, find it and check its labels:

gh issue view <N> --repo nota-daw/nota --json number,title,labels,state

It must be open and carry approved (or good first issue / help wanted). If there is no issue or it isn't approved, stop and tell the user: they open the issue (offer to draft its text) and wait for the label. Don't open the PR "to discuss" instead. Compare the change with what the issue agreed; if it goes further, split it or get the issue's scope extended first. Only release PRs cut by core contributors skip this step.

1. Branch and commit

  • Branch from develop (never main): git checkout -b <type>/<slug> — fix/…, feat/…, docs/…, chore/…. If the work is already on develop uncommitted, create the branch first; the working tree comes along.
  • scripts/build.sh (or build-linux.sh / build-win.ps1) must pass — it runs the smoke test.
  • Commit message: (fix) Summary, (feat) …, (docs) …, (refactor) …, (style) …; a body that says what and why in plain words. No AI attribution (no Co-Authored-By, no "Generated with" line) in commits or the PR body.
  • Author and committer: whoever makes the change, from their own git config. Never set user.name / user.email / --author to someone else's identity.
  • Spec and bug artifacts (specs/<slug>/, .specify/bugs/<slug>/) ship with the change they describe. Never commit build dirs, .cpm-cache/, benchmark output or harness binaries.

2. Decide what evidence the PR needs

| The change… | Attach | |---|---| | alters anything the user sees (a window, panel, device card, menu, theme, layout, custom-drawn view) | before / after screenshots, same size, theme and content | | aims at or may affect performance (engine render path, DSP, threads, allocation, CPU, memory, startup) | benchmark: before vs after (and vs the last good build when fixing a regression), with charts + a table | | both | both | | neither (docs, refactor with no runtime effect, CI) | nothing — say so in the Summary |

When unsure whether a change is user-visible, run the app and look.

3. Screenshots (UI changes)

  1. Capture before on the base commit and after on the branch, with the same window size, theme (default Studio Dark unless the change is theme-specific — then one pair per theme), interface scale and project content. Reuse the capture tooling the nota-design / nota-docs skills describe (headless Avalonia render or the app's own capture hook) rather than hand screenshots, so both shots are pixel-comparable.
  2. Name them <what>-before.png / <what>-after.png; a side-by-side <what>-both.png is welcome for small changes.

4. Benchmarks (performance changes)

Two layers, and a performance change needs both:

  • Regression guards — tests/Nota.SmokeTest/RenderPoolTests.cs, part of every smoke run (scripts/build.sh, CI on all three platforms; alone: dotnet run --project tests/Nota.SmokeTest -c Release -- --perf). Hardware-independent checks: render threads idle at ~0 CPU (their own thread clocks), parallel vs single-thread CPU ratios while playing and bouncing, bounce not slower than one thread, bit-identical output, tracks edited while rendering. When you touch the render path, threading or allocation, keep these green; when you fix a performance bug, add a guard here that fails on the old code (prove it: put the old behaviour back briefly and watch the check fail).
  • Benchmark numbers for the PR description, below.

The engine benchmark is in the repo:

  • scripts/bench-engine.sh [-r runs] <out-dir> <label>=<engine-lib-dir> ... — links scripts/bench/engine-bench.cpp against each Release libnota_engine and runs idle, offline render (bounce) and real-time-paced scenarios for audio and synth tracks, interleaving the builds run by run. Writes results.csv + machine.txt.
  • scripts/bench-chart.py <out-dir> <label>="Display name" ... — medians, three charts (cpu-playing, bounce-time, bounce-cpu; SVG + 2x PNG) and summary.md (tables + machine).

Recipe:

  1. Build each revision you compare in Release, each in its own checkout so nothing is shared: git worktree add --detach /tmp/nota-<label> <commit>, then configure + ninja nota_engine in its src/native/nota.engine/build. Revisions before the CPM switch (#212) need git submodule update --init --recursive --depth 1 first. The branch itself can use the main build/ dir (it must stay Release).
  2. Copy each libnota_engine.* into its own folder (/tmp/bench/libs/<label>/) so later rebuilds don't change what you measured.
  3. Run on a quiet machine, on power, ≥3 runs: scripts/bench-engine.sh -r 3 /tmp/bench/out before=… after=…. Look at the spread in results.csv; rerun if runs disagree a lot.
  4. Chart it: scripts/bench-chart.py /tmp/bench/out before="Before" after="This PR". Open the PNGs and check them (labels, overlap) before attaching.
  5. Report honestly: put regressions in the table too and say why they're acceptable or what follows up. A benchmark also needs the commits measured and the machine (from machine.txt).

If the change needs a scenario the harness lacks, extend engine-bench.cpp (stick to C ABI functions every compared build exports) and the scenario list in bench-engine.sh, in the same PR.

5. Put the assets on pr-assets

One folder per PR, named after the change or issue (fix-pr212-review/, issue-223/). Commit on top of pr-assets — never force-push or rewrite it; old PRs link to its files.

git fetch origin pr-assets
git worktree add /tmp/nota-assets origin/pr-assets -B pr-assets
mkdir -p /tmp/nota-assets/<folder> && cp <pngs> <results.csv> <summary.md> /tmp/nota-assets/<folder>/
git -C /tmp/nota-assets add <folder>
git -C /tmp/nota-assets commit -m "Images for <change>"
git -C /tmp/nota-assets -c credential.helper= -c credential.helper='!gh auth git-credential' \
    push https://github.com/nota-daw/nota.git HEAD:pr-assets
git worktree remove /tmp/nota-assets

For benchmarks commit the CSV and summary.md next to the charts, so the numbers stay checkable. Embed with https://raw.githubusercontent.com/nota-daw/nota/pr-assets/<folder>/<file>.png.

6. Push and open the PR

  • Push over HTTPS (SSH push to nota-daw/nota is denied): git -c credential.helper= -c credential.helper='!gh auth git-credential' push -u https://github.com/nota-daw/nota.git <branch>, then git fetch origin <branch> && git branch -u origin/<branch>.
  • gh pr create --repo nota-daw/nota --base develop --head <branch> --title "<commit-style title>" --body-file <file>.
  • Body: follow .github/PULL_REQUEST_TEMPLATE.md (Summary, Spec, Checklist — tick only what was actually done; leave platforms you didn't build unticked). Add sections as needed:
    • Screenshots — a table, before | after: | Before | After | / |---|---| / | ![before](raw-url) | ![after](raw-url) |
    • Benchmark — the charts, the summary.md tables, the commits measured, the machine, and a sentence on how to reproduce (scripts/bench-engine.sh …).
    • Testing — what was run and what was not.
    • Link the approved issue (Closes #N / Refs #N) — required — and, for review follow-ups, the PR being followed up.
  • Base is develop. Don't enable auto-merge; don't merge.

Related Skills

View on GitHub
GitHub Stars0
CategoryDevelopment
Updated1d ago
Forks0

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low
nota-pr — Gemini Rules: Install & Safety Check | SkillAgent