Agent skill

Change Boot

by tikalk in tikalk/adlc-team-skills

A skill your agent uses when past-change rationale matters (refactoring unfamiliar code, revert or hotfix analysis, issue-linked commit archaeology, session authors git changes with human-authored…

MITAuto-check passedDevelopment

Install Change Boot

skills CLI
$ npx skills add tikalk/adlc-team-skills --skill change-boot -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tikalk/adlc-team-skills change-boot --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/change/change-boot .claude/skills/change-boot && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
change-boot
GitHub stars
141
Token cost
~1.8k tokens
SKILL.md length
857 words
Files
1
Skills in repo
44
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when past-change rationale matters (refactoring unfamiliar code, revert or hotfix analysis, issue-linked commit archaeology, session authors git changes with human-authored…

  • Works in 3 steps: Locate the ChDR Index → Inject ChDR Context (Output Contract) → Capture Change Rationale
  • Past-change rationale matters (refactoring unfamiliar code
  • SKILL.md covers Overview, When to Use, Core Process and Absent Context, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Change Boot is an agent skill from tikalk/adlc-team-skills. Use when past-change rationale matters (refactoring unfamiliar code, revert or hotfix analysis, issue-linked commit archaeology, session authors git changes with human-authored messages) — injects the published ChDR index (docs/adlc/memory/chdr.md, legacy .adlc/memory/chdr.md fallback) as session context; pairs history mining (/change-init) with routine capture (direct-write drafts clarified via /change-clarify); invoked from team-boot's Class Boots catalog.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Refactoring and Git workflow. It works with Git. The repository describes itself as: Agent skills for the Agentic SDLC: team lifecycle (team-boot, team-learn, team-init, team-repair), software factory, evals, CDR lifecycle with confidence scoring, and… The licence is MIT.

When your agent uses it

  • Past-change rationale matters (refactoring unfamiliar code
  • Hotfix analysis
  • Issue-linked commit archaeology
  • Session authors git changes with human-authored messages) — injects the published ChDR index (docs/adlc/memory/chdr.md

Example prompts

  • “/change-boot”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Locate the ChDR Index
  2. Inject ChDR Context (Output Contract)
  3. Capture Change Rationale

What it can do on your machine

Read from SKILL.md and the folder at commit 2dbed36. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Change Boot loads about 1.8k tokens when it runs. Until then it costs about 119 tokens; SKILL.md has 857 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~119
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tikalk/adlc-team-skills at commit 2dbed36, republished under its MIT licence (© tikalk). 857 words, ~1,766 tokens.

Download SKILL.mdSave it as .claude/skills/change-boot/SKILL.md (or your agent's skills folder).
name
change-boot
description
Use when past-change rationale matters (refactoring unfamiliar code, revert or hotfix analysis, issue-linked commit archaeology, session authors git changes with human-authored messages) — injects the published ChDR index (docs/adlc/memory/chdr.md, legacy .adlc/memory/chdr.md fallback) as session context; pairs history mining (/change-init) with routine capture (direct-write drafts clarified via /change-clarify); invoked from team-boot's Class Boots catalog.

change-boot

Overview

One of the five class boots surfaced by team-boot's Class Boots catalog. team-boot injects the always-relevant team context (constitution, CDR index, skills registry) at session start; this skill loads the change history layer on demand — the published ChDR index mined from git history — and pairs it with decision capture so change rationale is recovered (/change-init) rather than living only in commit messages.

Reading past rationale and recording new rationale are one loop: published ChDRs explain why the code looks the way it does; rationale discovered during the work flows back into the same record system.

When to Use

Invoke at the START of a matching task — before planning the todo list and before implementation — so the ChDR context informs planning. Never defer to session end.

Invoke when:

  • Refactoring or modifying unfamiliar code — check whether a ChDR explains the current shape before changing it.
  • Analyzing reverts, hotfixes, or fix chains ("why was this reverted?").
  • The session authors git changes with human-authored messages (commit/merge/ revert/rebase/cherry-pick/tag with an authored message, authored PR title/body, CHANGELOG edit) — evaluate at session end whether the rationale is non-obvious enough for a ChDR; routine ops with generated or empty messages are not ChDRs (proportionality gate).
  • The session produces change rationale: a revert/hotfix explanation, or a commit that links to an issue tracker (the /change-init mining signal).

Core Process

Step 1: Locate the ChDR Index

From the current working directory (do NOT walk up parent directories):

  • Primary: docs/adlc/memory/chdr.md (generated by /change-publish; rows start with | ChDR)
  • Fallback: .adlc/memory/chdr.md (legacy layout, pre-ADR-401)

If the index is missing but docs/adlc/memory/chdr/ChDR-*.md or legacy .adlc/memory/chdr/ChDR-*.md files exist, synthesize a lean table from each file (ID from filename; Title/Status from frontmatter or first heading). If nothing exists, report 0 ChDRs — never fabricate rows.

When no local memory index exists in the current working directory and the directory sits inside a workspace (detected via a .gitmodules marker in an ancestor), read the workspace root's docs/adlc/memory/ index instead (ADR-401 dual-read order applies: docs/adlc/memory first, legacy .adlc/memory fallback).

Step 1b: Read the ChDR Drafts Index

Check .adlc/drafts/chdr/ for ChDR-*.md files with status: proposed or status: discovered in frontmatter. These are draft ChDRs pending clarification — frontmatter proposed/discovered maps to ledger Status captured, and both feed the Unclarified count. Collect ID / Title / Type / Status / Date from each file. If the directory is empty or absent, report 0 pending drafts.

Absent Context

If team-boot injected no team context this session (no Team Context & Decisions section in the first user message — unconfigured project or hook failure): say so in one line, emit the section heading with a 0 ChDRs matched (no team context injected — run /team-setup) source line, and continue the task on the directly-read ChDR index. Never treat a missing injection as an empty record set. Recovery: run /team-diagnose.

Step 2: Inject ChDR Context (Output Contract)

Emit before the task answer:

markdown
## ChDR Context

| ID | Title | Status | Date |
|--|--|--|--|
| ChDR-001 | Why payments retries are capped at 3 | stable | 2026-08-16 |

_Searched N ChDRs, K matched._

## Drafts Pending Review

| ID | Title | Type | Status | Date |
|----|-------|------|--------|------|
| (from .adlc/drafts/chdr/) |

_Unclarified: N ChDR drafts — run /change-clarify to review._
  • Render ID / Title / Status / Date from the index (the full index also carries Issue, Commit, Note — read the individual ChDR-*.md when a task matches a row).
  • N = total index rows; K = rows relevant to the current task. K MUST equal the table rows shown. 0 rows matched → emit the section heading + the _Searched N ChDRs, K matched._ line only — no table. A 0-row table header collapses into unrendered single-line markdown; never emit one. Emit the section as markdown blocks — heading, table rows, and counts line each on their own lines.
Show full SKILL.md (295 more words)Show less
Step 3: Capture Change Rationale
TriggerAction
Revert or hotfix performed/analyzed with rationaleChDR → direct write to .adlc/drafts/chdr/
Commit authored that links to an issue trackerChDR → direct write to .adlc/drafts/chdr/ post-merge
Git command authored in-session with a human-authored message, authored PR title/body, or CHANGELOG editevaluate at session end: non-obvious rationale → ChDR direct write to .adlc/drafts/chdr/; routine ops skipped (proportionality gate)
Fix chain discovered in historyChDR → direct write to .adlc/drafts/chdr/
ChDR-class decision already in the ledgerverify capture happened; if not, re-surface

Add/refresh rows in Team Context & Decisions (ID | Name | Type | Rel | Status | Clarify) for every ChDR-class decision detected this session — including ones from before this boot was invoked. Mirror each decision as a task-list todo (draft → /change-clarify at session end); after code-modifying tasks, add a trailing todo to sweep Team Context & Decisions until Unrecorded: 0 pending · Unclarified: 0 drafts (a draft leaves Unclarified only via its clarify skill or an explicit user handoff to a named clarify or execute skill). At session end, deliver the clarify prompt naming each captured ChDR draft in .adlc/drafts/chdr/ (ID + skill), covering post-merge issue-linked commits too; if the user defers clarify, mark those rows handed off.

Failure Handling

  • Missing index + missing records → emit the section heading + _Searched 0 ChDRs, 0 matched._ only — no table — and continue the user's task; never block.
  • Unparseable index rows → skip malformed rows, note the skip count.

Red Flags

  • Fabricating ChDR rows or inflating K beyond the table shown.
  • Injecting the index but ignoring capture — the pairing is the point.
  • Walking up parent directories to find .adlc/.
  • Mining rationale without SHA/URL provenance — /change-clarify will reject Decision claims that lack it.

Verification

  • ChDR Context table emitted with _Searched N ChDRs, K matched._ (K = table rows).
  • Detected ChDR-class decisions added as Team Context & Decisions rows.

© tikalk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/change/change-boot of tikalk/adlc-team-skills.

Open the folder on GitHubat commit 2dbed36

Compare with similar skills

Change Boot next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Change Boot compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Change Boot this skilltikalk/adlc-team-skills141—~1.8kAutomated safety check: PassMIT
Merge Masterkeybase/client9.3k—~1.3kAutomated safety check: PassBSD-3-Clause
Docs Update from DiffQwenLM/qwen-code28k—~1.1kAutomated safety check: PassApache-2.0
Refactor Command To Commandlineresultruby-git/ruby-git1.8k—~1.3kAutomated safety check: PassMIT
Nemo Rl Auto ResearchNVIDIA/skills3.5k—~2.3kAutomated safety check: PassApache-2.0
Semantic Szz Analyzermajiayu000/claude-skill-registry6661 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Merge Master

    keybase/client

    A skill your agent uses when periodically merging upstream master commits into a long-running refactor branch where code has moved, been renamed, or restructured — guiding careful per-commit…

    9.3k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Docs Update from Diff

    QwenLM/qwen-code

    Reads local git changes and updates only the matching docs pages, so documentation stays in sync with uncommitted or recent code changes.

    28k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Migrates a command class that still performs parsing or custom execution logic to return raw Git::CommandLine::Result, moving parsing to facade/parser layers.

    1.8k GitHub stars~1.3k tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • Official

    Autonomous NeMo-RL research agent workflow for directed hypothesis testing and open-ended discovery.

    3.5k GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Semantic Szz Analyzer

    majiayu000/claude-skill-registry

    Identify bug-introducing commits using semantic analysis that extends traditional SZZ algorithm.

    666 GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

More from tikalk/adlc-team-skills

All 44 skills in this repo
  • Team Boot

    tikalk/adlc-team-skills

    A skill your agent uses when a session starts or resumes after compaction (auto via the sessionstart and sessioncompact event hooks) and the team AI directives context — constitution, CDR index…

    141 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Architect Clarify

    tikalk/adlc-team-skills

    A skill your agent uses when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation.

    141 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed
  • Change Clarify

    tikalk/adlc-team-skills

    A skill your agent uses when reviewing, accepting, rejecting, or deferring ChDRs mined by change-init, validating inferred decisions against their git and issue evidence before promotion to project…

    141 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Change Init

    tikalk/adlc-team-skills

    A skill your agent uses when you want guided mining of git history, structured change-story clustering, or comprehensive rationale recovery before documenting.

    141 GitHub stars~3.5k tokensUpdated yesterday
    Auto-check passed
  • Change Publish

    tikalk/adlc-team-skills

    A skill your agent uses when accepted ChDRs are ready for promotion from drafts to project memory at docs/adlc/memory/chdr/ and the boot-facing chdr.md index needs regenerating.

    141 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Evals Analyze

    tikalk/adlc-team-skills

    A skill your agent uses when evaluation results need triage and loop-closing — spec failures route to deterministic checks or context rules, generalization failures to the evaluator backlog.

    141 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Change Boot

What does Change Boot do?

A skill your agent uses when past-change rationale matters (refactoring unfamiliar code, revert or hotfix analysis, issue-linked commit archaeology, session authors git changes with human-authored…. Change Boot is an agent skill from tikalk/adlc-team-skills.md fallback) as session context; pairs history mining (/change-init) with routine capture (direct-write drafts clarified via /change-clarify); invoked from team-boot's Class Boots catalog.

When should I use Change Boot?

Change Boot fits situations like: past-change rationale matters (refactoring unfamiliar code; hotfix analysis; issue-linked commit archaeology; session authors git changes with human-authored messages) — injects the published ChDR index (docs/adlc/memory/chdr.md.

How do I install Change Boot in Claude Code?

Run `npx skills add tikalk/adlc-team-skills --skill change-boot -a claude-code`. Or copy the skill folder (skills/change/change-boot in tikalk/adlc-team-skills) into .claude/skills/change-boot in your project. Claude Code loads it when a task matches its description.

How do I install Change Boot in Codex?

Run `npx skills add tikalk/adlc-team-skills --skill change-boot -a codex`. Or copy the skill folder (skills/change/change-boot in tikalk/adlc-team-skills) into .agents/skills/change-boot in your project. Codex loads it when a task matches its description.

Can I use Change Boot in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tikalk/adlc-team-skills --skill change-boot -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/change-boot, .gemini/skills/change-boot, .github/skills/change-boot and .opencode/skills/change-boot in your project.

What does Change Boot need to run?

SKILL.md names no scripts, command-line tools or credentials: Change Boot is instructions for the agent only.

Does Change Boot access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Change Boot safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Change Boot use?

Change Boot is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Change Boot use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Change Boot?

Skills that share tags, products or a category with Change Boot: Merge Master (keybase/client, 9.3k stars), Docs Update from Diff (QwenLM/qwen-code, 28k stars), Refactor Command To Commandlineresult (ruby-git/ruby-git, 1.8k stars) and Nemo Rl Auto Research (NVIDIA/skills, 3.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Change Boot?

tikalk (a GitHub organization) maintains it in tikalk/adlc-team-skills, which has 141 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 6, 2026.

Source: tikalk/adlc-team-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.