repo-release-governance

Use when working on learn-likecc and the task involves new requirements, roadmap updates, README updates, git commits, GitHub Pages updates, or release/version changes. Ensures every new requirement is written into plan files, unfinished work remains in TODO sections, and release/git/pages handling follows the repo workflow without the user needing to restate it each time.

Jump to install

Repository: Harzva/learn-likecc
Last source activity: April 8, 2026 at 13:11
Detected SKILL.md language: English
Stars: 57
Forks: 6

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/Harzva/learn-likecc --skill repo-release-governance

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Repo Release Governance

Use this skill for learn-likecc whenever the work touches:

new user requirements

roadmap or milestone changes

README positioning / TODO updates

git commits

GitHub Pages related updates

release / version / changelog updates

Mandatory workflow

Every new user requirement must be recorded in a plan file. Preferred file:

.claude/plans/likecode-model-freedom-roadmap.md If the requirement belongs elsewhere, add it to the relevant plan too.

Every unfinished requirement must remain visible in README TODO sections. Do not quietly drop pending work after discussing it. If something is proposed but not implemented, keep it in:

README.md
relevant .claude/plans/*.md

When a feature is finished:

mark it complete in the relevant plan
update README checklists
add a short real-demand mapping when useful

When the work affects release shape: always check and update these if relevant:

CHANGELOG.md
visible version strings
release/tag baseline
Pages-facing README/site copy if user-facing behavior changed

When committing:

keep commits scoped to the current task
avoid mixing unrelated dirty worktree changes
summarize what was included and what was intentionally excluded

Persistent assumptions for this repo

The user expects requirements to be tracked, not just discussed.

The repo tradition is: completed items get check marks, pending items stay in TODO.

Git / Pages / Release work should not require repeated reminders from the user.

Minimum checklist before finishing a task

Was the new requirement written into a plan?

If not finished, is it still present in README TODO?

If finished, did we mark it complete in README/plan?

If user-facing, did we update release/version/changelog context?

If committing, did we keep the commit scoped?