Skip to content
cccskills
FreePublished on GitHub

whatchanged

List features added to Kolu during a timeframe, grouped by product area and linked to PRs. Use when asked "what changed in kolu since …" or to draft release notes.

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

juspay/kolu
Works withGitHub
See how to install

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

List features added to Kolu during the timeframe the user names (e.g. "last week", "last 2 weeks", "since 2026-03-01").

Instructions

  1. Determine the repo from git remote get-url origin. Run gh pr list --repo <owner/repo> --state merged --search "merged:>=$(date -d '<timeframe> ago' +%Y-%m-%d 2>/dev/null || date -d '<timeframe>' +%Y-%m-%d 2>/dev/null)" --json number,title,mergedAt,url --limit 200 to get merged PRs in the timeframe. If the date parsing fails, fall back to git log --since="<timeframe>" --merges --oneline and correlate with gh pr list --state merged.
  2. Filter to user-facing changes — skip pure refactors, CI fixes, test-only changes, docs-only changes, and dependency bumps unless they unlock a visible feature.
  3. For each PR, read the PR title and body (via gh pr view <number>) to understand what changed.
  4. Group notable features by area (e.g. Terminal, Sidebar, Theme, Networking, Developer Experience). Within each area, lead with the biggest feature, then list related smaller ones. Put minor fixes/polish in a flat "Minor" section at the end.

Output format

## What changed in Kolu (the timeframe)

### Area Name

- **Short description of feature** — one-line explanation. [#123](url)
- Related smaller feature. [#124](url)

### Another Area

- **Feature** — explanation. [#200](url)

### Minor

- Short description. [#456](url)
- ...

Keep descriptions concise and user-facing (what it does for the user, not implementation details). Link every item to its PR. Choose area names that reflect what the user cares about, not internal module names.

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

blog-post

Free

Write a kolu blog post grounded in the real build history — mine the Claude Code session logs behind a feature for the actual story (for large efforts, fan out over the transcripts with an ultracode workflow), draft it in the author's voice, and wire it into the Astro site. Use when asked to write a blog post or engineering essay about something that was built, especially one that should read as a narrative of what actually happened rather than invented marketing copy.

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

juspay/kolu82Updated Oct 22, 2026

ci

Free

Run this repo's CI end-to-end — kolu's policy on top of the odu runner: banned opt-out flags, x86_64-linux pinning, pool upkeep, fail-fast surfacing, e2e timing evidence, and the green-gate. Triggers on "run CI", "drive CI", "re-run the pipeline", "close the red check", "warm the pool". Runner mechanics live in the `/odu` skill.

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

juspay/kolu82Updated Oct 22, 2026

dev-server

Free

Launch the kolu dev server on two RANDOM free ports so it never collides with the running production `kolu.service`, remember the ports for the rest of the session, and tear down only the dev instance. Load before running the app locally — for evidence capture, driving a live kolu with the chrome-devtools MCP, or any `just dev` you'd otherwise run by hand. Triggers on "run kolu locally", "launch the dev server", "boot kolu", "drive a live kolu", "start the app to screenshot it", or before pointing chrome-devtools at a local kolu.

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

juspay/kolu82Updated Oct 22, 2026

diataxis

Free

Classify, write, and audit documentation per Diátaxis (diataxis.fr) — the four-quadrant method (tutorials · how-to guides · reference · explanation). Encodes the compass as a decision procedure, each quadrant's contract as hard rules, and an executable mixed-mode audit. Project-agnostic; the per-repo doc-location mapping lives in a repo rule of the project's own (kolu: the Kolu overlay below). Use when writing any user-facing doc, structuring a docs site, or auditing existing docs for mixed modes.

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

juspay/kolu82Updated Oct 22, 2026

dock-state

Free

The Dock's agent-state folds — one fenced source of truth in @kolu/terminal-vocab, the load-bearing order≠colour split, and the one "is something happening" question. Use when editing agentProjection or the canvas dock.

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

juspay/kolu82Updated Oct 22, 2026

e2e-testing

Free

E2E test conventions — semantic selectors, arrange-steps that prove the process started, runtime markers that cannot match the shell echo, and absolute-path tool invocations. Use when writing or changing a .feature scenario under packages/tests.

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

juspay/kolu82Updated Oct 22, 2026

See all skills by juspay

Report a problem with this skill