changelog-release-notes

Maintain Con's CHANGELOG.md and release notes. Use when updating changelog entries, preparing a beta/dev release, reviewing PR release-note coverage, or ensuring contributor PR credit is present.

الانتقال إلى التثبيت

المستودع: nowledge-co/con-terminal
آخر نشاط في المصدر: ٧ مايو ٢٠٢٦ في ٠٥:٠٥
لغة SKILL.md المكتشفة: الإنجليزية
النجوم: ٥٥٦
التفرعات: ٤٤

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.

npx skills add https://github.com/nowledge-co/con-terminal --skill changelog-release-notes

يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.

تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.

مراجعة ملفات المصدر

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

SKILL.md

تعليمات المصدر · معاينة للقراءة فقط

العودة إلى البحث العودة إلى التثبيت

release

Run and verify Con beta, dev, and stable releases without publishing incomplete artifacts.

2026-08-27

con-cli-e2e

Validate Con's local socket control plane against a real running app session, and write/run con-test integration tests. Use when testing con-cli, the Unix socket API, pane control, tmux control, in-session agent calls, or when writing E2E test cases in crates/con-test/testdata/.

2026-05-08

terminal-agent-benchmark

Run and maintain Con's terminal-agent benchmark against a live app session. Use when validating con-cli, SSH workspace reuse, tmux awareness, agent-target preparation, or when collecting benchmark evidence for regressions and release notes.

2026-04-30

عرض الكل من هذا المستودع

Changelog Release Notes

Use this skill whenever CHANGELOG.md, PR release notes, or release summaries are touched.

Workflow

Verify the latest released beta before choosing a heading:

git fetch --tags origin
git tag --sort=-v:refname | rg '^v[0-9]+\\.[0-9]+\\.[0-9]+-beta\\.' | head
gh release view <tag> when GitHub release state matters

Put pending work under the next unreleased beta only. If the latest shipped beta is v0.1.0-beta.63, the top unreleased heading is v0.1.0-beta.64; do not create beta.65 until beta.64 is tagged and released.

Gather PR and author context for every entry:

gh pr view <number> --json number,title,author,url,mergedAt
for merged work, git log <latest-tag>..HEAD --merges --oneline helps find the included PRs

Every PR-derived changelog bullet must end with PR and author credit:

_(PR [#149](https://github.com/nowledge-co/con-terminal/pull/149) by [@sundy-li](https://github.com/sundy-li))_

Credit contributors exactly by GitHub login. Preserve external contributor credit even when follow-up commits refine the same feature.

Keep shipped historical sections stable. Only edit old sections to correct a factual mistake, missing credit, or broken link.

Writing Rules

Write for users first: describe the visible behavior or benefit, not the internal implementation unless it explains a risk or platform boundary.

Use Added, Changed, and Fixed sections. Group bullets under concise audience/platform labels such as macOS, Windows, Linux, Panes, or Developer Experience.

Do not mention "workspace restore" or other baseline continuity as novelty unless the user-facing behavior truly changed. Default expected behavior should read as polish or reliability, not marketing.

Add release dates only when a version is actually tagged/released.

If a bullet combines multiple PRs, include all relevant PR/author credits.

Validation

Confirm the heading matches the latest shipped beta plus one.

Confirm every new PR-derived bullet has PR [#...] and by [@...].

Run python3 scripts/docs/validate-manifest.py when docs routing may be affected.

Run git diff --check before committing.