Menu

Individual skill

writing-modpack-devlog

Use when starting or appending to a modpack project dev-log. Creates <project>/docs/dev-log.md if absent; appends a dated entry on subsequent calls. Triggers - 'log this', 'add to dev log', 'record what I did', 'note this change', 'devlog'.

plugins/BB-84C/bgs-modding-superpowers/skills/writing-modpack-devlog/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,535
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

The modpack dev-log is the durable record of what the curator did to the modpack, in chronological order, with enough context for a future maintainer to understand why a change happened. This skill replaces the deleted `templates/modpack/dev-log.md` template by creating `<project>/docs/dev-log.md` at runtime, then appending entries as the modpack evolves.

## When to Use

| Use this skill when... | Result |
| --- | --- |
| The user says "log this", "add to dev log", "record what I did", or "note this change" | Append a dated entry to the project dev-log. |
| A mod was added, removed, replaced, upgraded, downgraded, patched, or moved in load order | Record what changed and why. |
| A conflict-audit session finished | Summarize the finding and link evidence from `xedit-conflict-audit` or `xedit-automation` output. |
| A CTD, freeze, missing asset, bad facegen, navmesh issue, or broken quest was investigated | Preserve the investigation result, even if the fix is not final. |
| A modpack release was cut | Add the curator-facing note and cross-link to `writing-modpack-changelog`. |
| The user made a manual decision that future agents must not re-litigate | Record the decision, context, and evidence. |