원클릭으로 Manus에서 모든 스킬 실행

godmode-changelog

스타1

포크1

업데이트2026년 7월 3일 00:53

Parse git history into structured changelogs. Use to generate release notes, audit commit conventions before tagging, or integrate with `godmode release` workflow.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

89jobrien

89jobrien/godmode

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Changelog

When to Use

Before a release — to audit commits and generate release notes
To understand what changed since the last tag
To flag commits that do not follow conventional-commit format
To group commits by type and affected crate
To integrate with godmode release changelog subcommand

Conventional Commit Format

Commits should follow the pattern:

<type>(<scope>): <description>

Type (required): feat, fix, refactor, chore, docs, test, ci
Scope (optional): the affected crate or module, e.g. godmode-core, godmode-cli
Description (required): concise summary of the change

Examples:

feat(godmode-core): add changelog generator
fix(godmode-cli): handle missing config file
refactor: unify error handling in dispatch module
docs: update CLI reference
test: add property tests for graph cycles

Parsing Rules

Extract type from the commit message prefix (word before ( or :)
If the type is not in the canonical list, mark as non-conventional
Extract scope from parentheses, if present (e.g. godmode-core)
Extract description from the text after : or after the type
Group commits by type, then by scope/crate

Output Format

Produce grouped markdown changelog:

# Changelog — <tag>..HEAD

## Features

### <crate>

- <commit description>
- <commit description>

## Fixes

### <crate>

- <commit description>

## Refactoring

...

## Other

...

## Non-Conventional Commits

- <full commit message> (reason: missing type, scope, or separator)

Omit sections with no entries. "Other" includes docs, test, chore, ci and commits without a crate scope.

Integration with Release Workflow

Write the generated changelog to CHANGELOG.md or .ctx/ manually and commit. (godmode release changelog generates and prepends an entry from commits since the last tag; this skill is for authoring richer notes and writing them with the Write tool.)

Guardrails

Never fabricate commits — read only from git log
Never rewrite git history
Never commit changes without explicit instruction
Flag all non-conventional commits; do not silently omit them
If asked to reword commits, refuse — use git rebase outside godmode

이 저장소의 다른 Skills

같은 저장소

godmode-introspection

89jobrien/godmode

Audit godmode skills, agents, and plugin files for internal consistency, broken references, stale commands, and cross-skill contradictions. Use when asked to "introspect", "audit the skills", "review godmode", or after adding new skills.

2026-07-071

godmode-using-godmode

89jobrien/godmode

Use at the start of every conversation to orient to available skills and workspace rules. Replaces superpowers entirely. Triggers on session start, "/godmode", or "what skills do you have".

2026-07-071

godmode-memory-banking

89jobrien/godmode

Generate and maintain a `.ctx/godmode/memory-bank/` directory that captures project context backed by source code. The memory bank is injected into prompts via lifecycle hooks and updated incrementally as work progresses. Use when starting a new project, onboarding to an unfamiliar codebase, or when context drift is detected.

2026-07-031

godmode-agent-governance

89jobrien/godmode

Patterns and techniques for adding governance, safety, and trust controls to AI agent systems in Rust. Use this skill when building agents that call external tools, implementing policy-based access controls, adding semantic intent classification to detect dangerous prompts, creating trust scoring systems for multi-agent workflows, building audit trails, or enforcing rate limits and content filters. Covers policy composition, tool wrappers, trust decay, and JSONL audit trails — all in Rust.

2026-07-031

godmode-dead-code

89jobrien/godmode

Dead code detector for Rust workspaces. Finds unused public API surface, orphaned test helpers, stale feature flags, and plugin artifacts referencing removed CLI subcommands. Cross-references pub exports against call sites across the workspace.

2026-07-031

godmode-issue-triage

89jobrien/godmode

Triage and prioritize GitHub issues by type (bug/feature/chore), complexity (S/M/L), and priority (P1-P4). Detect duplicates, propose execution order, and generate task graphs for godmode automation.

2026-07-031

Changelog

When to Use

Before a release — to audit commits and generate release notes

To understand what changed since the last tag

To flag commits that do not follow conventional-commit format

To group commits by type and affected crate

To integrate with godmode release changelog subcommand

Conventional Commit Format

Commits should follow the pattern:

<type>(<scope>): <description>

Type (required): feat, fix, refactor, chore, docs, test, ci

Scope (optional): the affected crate or module, e.g. godmode-core, godmode-cli

Description (required): concise summary of the change

Examples:

feat(godmode-core): add changelog generator fix(godmode-cli): handle missing config file refactor: unify error handling in dispatch module docs: update CLI reference test: add property tests for graph cycles

Parsing Rules

Extract type from the commit message prefix (word before ( or :)

If the type is not in the canonical list, mark as non-conventional

Extract scope from parentheses, if present (e.g. godmode-core)

Extract description from the text after : or after the type

Group commits by type, then by scope/crate

Output Format

Produce grouped markdown changelog:

# Changelog — <tag>..HEAD ## Features ### <crate> - <commit description> - <commit description> ## Fixes ### <crate> - <commit description> ## Refactoring ... ## Other ... ## Non-Conventional Commits - <full commit message> (reason: missing type, scope, or separator)

Omit sections with no entries. "Other" includes docs, test, chore, ci and commits without a crate scope.

Integration with Release Workflow

Guardrails

Never fabricate commits — read only from git log

Never rewrite git history

Never commit changes without explicit instruction

Flag all non-conventional commits; do not silently omit them

If asked to reword commits, refuse — use git rebase outside godmode

name	godmode:changelog
description	Parse git history into structured changelogs. Use to generate release notes, audit commit conventions before tagging, or integrate with `godmode release` workflow.
requires	[]
next	["release-notes"]

name	godmode:changelog
description	Parse git history into structured changelogs. Use to generate release notes, audit commit conventions before tagging, or integrate with `godmode release` workflow.
requires	[]
next	["release-notes"]