Files
uroma b60638f0a3 Add community skills, agents, system prompts from 22+ sources
Community Skills (32):
- jat: jat-start, jat-verify, jat-complete
- pi-mono: codex-cli, codex-5.3-prompting, interactive-shell
- picoclaw: github, weather, tmux, summarize, skill-creator
- dyad: 18 skills (swarm-to-plan, multi-pr-review, fix-issue, lint, etc.)
- dexter: dcf valuation skill

Agents (23):
- pi-mono subagents: scout, planner, reviewer, worker
- toad: 19 agent configs (Claude, Codex, Gemini, Copilot, OpenCode, etc.)

System Prompts (91):
- Anthropic: 15 Claude prompts (opus-4.6, code, cowork, etc.)
- OpenAI: 49 GPT prompts (gpt-5 series, o3, o4-mini, tools)
- Google: 13 Gemini prompts (2.5-pro, 3-pro, workspace, cli)
- xAI: 5 Grok prompts
- Other: 9 misc prompts (Notion, Raycast, Warp, Kagi, etc.)

Hooks (9):
- JAT hooks for session management, signal tracking, activity logging

Prompts (6):
- pi-mono templates for PR review, issue analysis, changelog audit

Sources analyzed: jat, ralph-desktop, toad, pi-mono, cmux, pi-interactive-shell,
craft-agents-oss, dexter, picoclaw, dyad, system_prompts_leaks, Prometheus,
zed, clawdbot, OS-Copilot, and more
2026-02-13 10:58:17 +00:00

1.9 KiB

description
description
Audit changelog entries before release

Audit changelog entries for all commits since the last release.

Process

  1. Find the last release tag:

    git tag --sort=-version:refname | head -1
    
  2. List all commits since that tag:

    git log <tag>..HEAD --oneline
    
  3. Read each package's [Unreleased] section:

    • packages/ai/CHANGELOG.md
    • packages/tui/CHANGELOG.md
    • packages/coding-agent/CHANGELOG.md
  4. For each commit, check:

    • Skip: changelog updates, doc-only changes, release housekeeping
    • Determine which package(s) the commit affects (use git show <hash> --stat)
    • Verify a changelog entry exists in the affected package(s)
    • For external contributions (PRs), verify format: Description ([#N](url) by [@user](url))
  5. Cross-package duplication rule: Changes in ai, agent or tui that affect end users should be duplicated to coding-agent changelog, since coding-agent is the user-facing package that depends on them.

  6. Add New Features section after changelog fixes:

    • Insert a ### New Features section at the start of ## [Unreleased] in packages/coding-agent/CHANGELOG.md.
    • Propose the top new features to the user for confirmation before writing them.
    • Link to relevant docs and sections whenever possible.
  7. Report:

    • List commits with missing entries
    • List entries that need cross-package duplication
    • Add any missing entries directly

Changelog Format Reference

Sections (in order):

  • ### Breaking Changes - API changes requiring migration
  • ### Added - New features
  • ### Changed - Changes to existing functionality
  • ### Fixed - Bug fixes
  • ### Removed - Removed features

Attribution:

  • Internal: Fixed foo ([#123](https://github.com/badlogic/pi-mono/issues/123))
  • External: Added bar ([#456](https://github.com/badlogic/pi-mono/pull/456) by [@user](https://github.com/user))