New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Change Clarify

by tikalk in 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…

MITAuto-check passedDevelopment

Install Change Clarify

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

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

GitHub CLI
$ gh skill install tikalk/adlc-team-skills change-clarify --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-clarify .claude/skills/change-clarify && 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-clarify
GitHub stars
141
Token cost
~2.9k tokens
SKILL.md length
1,086 words
Files
3 (incl. scripts)
Skills in repo
44
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 8 steps: Load Pending ChDRs → Detect Lightweight Draft Format → Pre-Validation → …
  • Deferring ChDRs mined by change-init
  • SKILL.md covers What this skill does, When to use, Process and Next Steps, plus 2 more sections
  • Runs Shell and PowerShell scripts from its folder; calls git

What it does

Change Clarify is an agent skill from tikalk/adlc-team-skills. Use when reviewing, accepting, rejecting, or deferring ChDRs mined by change-init, validating inferred decisions against their git and issue evidence before promotion to project memory.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts (for example `scripts/bash/setup-change-clarify.sh`).

It sits in Development, covering Agent memory. 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

  • Deferring ChDRs mined by change-init
  • Validating inferred decisions against their git and issue evidence before promotion to project memory

Example prompts

  • “/change-clarify”

Requirements

  • A Bash shell
  • PowerShell

Workflow steps

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

  1. Load Pending ChDRs
  2. Detect Lightweight Draft Format
  3. Pre-Validation
  4. Gap Identification
  5. Sequential Clarification
  6. Update ChDR Files
  7. Regenerate Index
  8. Summary

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

    Ships 2 files in scripts/ (Shell and PowerShell), which the agent can run.

    Shell commands in SKILL.md call:

    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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 Clarify loads about 2.9k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 1,086 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

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

Download SKILL.mdSave it as .claude/skills/change-clarify/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
change-clarify
description
Use when reviewing, accepting, rejecting, or deferring ChDRs mined by change-init, validating inferred decisions against their git and issue evidence before promotion to project memory.
disable-model-invocation
true

change-clarify

What this skill does

Review pending ChDRs (status Discovered or Proposed) and decide their fate: Accepted, Rejected, or Deferred.

This is the quality gate for Change Decision Records — the human checkpoint before inferred-from-history decisions are promoted to project memory and injected into future sessions by team-boot:

  • Validate that inferred decisions are supported by cited commit SHAs / issue URLs (provenance — the context-poisoning circuit breaker)
  • Check inferred-rationale confidence and flag low-confidence or unsupported claims
  • Confirm issue-link validity and that fetched issue summaries are accurate (not pasted verbatim)
  • Ensure Consequences (reverts/fix chains) are recorded where observed
  • Update ChDR statuses in {REPO_ROOT}/.adlc/drafts/chdr/ChDR-{NNN}.md
  • Regenerate {REPO_ROOT}/.adlc/drafts/chdr/chdr.md index

This is an interactive command. Present exactly one ChDR per interaction and wait for user input.

When to use

  • After /change-init: validate history-mined ChDRs before promotion
  • Periodic review: clean up stale pending ChDRs
When NOT to use
  • No pending ChDRs: if no ChDRs have status Discovered/Proposed, there is nothing to clarify
  • Reviewing CDRs: use /team-levelup (CDRs and ChDRs are distinct record types with separate gates)
  • Direct editing: do not use this skill to bypass the review workflow

Process

User Input
text
$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Examples of User Input:

  • "ChDR-001 ChDR-003" — focus on specific ChDRs
  • "all" — clarify all pending ChDRs
  • Empty input: clarify all ChDRs with status "Discovered" or "Proposed"
Flags
  • --all: clarify all pending ChDRs (same as empty input)
  • --limit N: limit to N clarifications per session (default: 5)
Role & Context

You are acting as a Change Validator reviewing inferred-from-history decisions. Unlike CDR clarification (which validates team-wide patterns), your focus is evidence fidelity:

  • Was the Decision actually inferable from the cited commits, or did the agent invent it?
  • Is the confidence level honest (a HIGH-confidence claim with a terse commit + no issue link is suspicious)?
  • Are issue summaries accurate and not leaking sensitive detail verbatim?
  • Are reverts/fix chains recorded where they exist (the highest-value content)?
ChDR Quality Checklist

Each ChDR should have:

  • ### Context explaining why the change happened (issue summary or commit messages)
  • ### Decision with inferred decision + confidence level
  • Every Decision claim cites a SHA or issue URL (provenance — non-negotiable)
  • ### Consequences (reverts/fix chains, or explicit "None observed")
  • ### Evidence with concrete SHAs, files, and issue links
  • Issue summaries are paraphrased, not raw paste (security)
  • Status is accurate
Outline
  1. Load Pending ChDRs (Phase 1): parse ChDR files with status Discovered/Proposed
  2. Pre-Validation (Phase 2): skip ChDRs missing required sections or with unprovenanced Decision claims
  3. Gap Identification (Phase 3): list clarification needs
  4. Sequential Clarification (Phase 4): one ChDR per interaction
  5. Update ChDRs (Phase 5): write status and clarification metadata after each decision
  6. Regenerate Index (Phase 6): update chdr.md
  7. Summary (Phase 7): present results
Execution Steps
Phase 1: Load Pending ChDRs

Run setup script:

bash
scripts/bash/setup-change-clarify.sh

Read all {REPO_ROOT}/.adlc/drafts/chdr/ChDR-*.md files and filter:

  • Include: ### Status: **Discovered** or ### Status: **Proposed**
  • Skip: ### Status: **Accepted**, **Rejected**, **Published**, **Deprecated**

If the setup script is unavailable or fails, resolve manually:

  1. REPO_ROOT — walk up from cwd to find .adlc/, or git rev-parse --show-toplevel.
  2. CHDR_DRAFTS_DIR — REPO_ROOT/.adlc/drafts/chdr
  3. PENDING_COUNT — count files with Discovered/Proposed status.

If no pending ChDRs:

text
No pending ChDRs found.
Run /change-init to mine git history first.
Step 0: Detect Lightweight Draft Format

Check if the draft being reviewed uses the lightweight draft template (indicated by presence of type, evidence, source, revisit-when fields in frontmatter and ## Rejected Alternatives / ## Reason body sections without the full formal template sections).

If lightweight:

  1. Read the draft's captured fields (Context, Decision, Rejected Alternatives, Reason)
  2. Transform to full formal template:
    • ADR: full MADR format with Decision Drivers, Considered Options, Pros/Cons, Constitution Alignment, Related ADRs
    • PDR: full PDR format with Market Forces, Consequences, Alternatives Considered, Links
    • ChDR: full ChDR format with Issue Links, Commits, Consequences, Evidence
    • CDR: full CDR format with Context Type, Target Module, Descriptor, Evidence
    • EVAL: full eval format with Error Analysis, Pass/Fail Examples, Implementation Notes
  3. Enrich from session context (add details the lightweight draft may have omitted)
  4. Present the enriched draft for review

If already full format, proceed with normal review.

Show full SKILL.md (432 more words)Show less
Phase 2: Pre-Validation

For each pending ChDR, check required sections:

  • ### Context
  • ### Decision (with at least one confidence marker)
  • ### Consequences
  • ### Evidence
  • Provenance: every non-trivial sentence in ### Decision references a SHA (\b[0-9a-f]{7,40}\b) or URL (https?://)

Skip invalid ChDRs and report:

markdown
## Skipped ChDRs

| ChDR | Issue | Action |
|---|---|---|
| ChDR-XXX | Decision claims lack SHA/URL provenance | Re-run /change-init or add evidence manually |
Phase 3: Gap Identification

Generate a gap report:

markdown
## ChDR Clarification Report

| ChDR | Title | Gap Type | Severity |
|---|---|---|---|
| ChDR-001 | [Title] | Low-confidence decision | MEDIUM |
| ChDR-002 | [Title] | Issue summary too verbose | LOW |

Gap types:

  • Low-confidence decision: Decision marked LOW confidence — consider rejecting or deferring
  • Unprovenanced claim: a Decision sentence without SHA/URL (should have been caught in Phase 2)
  • Issue summary too verbose: pasted verbatim instead of paraphrased (security)
  • Missing consequences: Consequences section empty but reverts observed in window
  • Stale: cluster's commits later reverted (the decision was reversed — mark for rejection or status reversal)
Phase 4: Sequential Clarification

CRITICAL: Present exactly ONE ChDR per interaction. Do NOT:

  • Present multiple ChDRs together
  • Auto-select actions
  • Proceed without explicit user input
  • Ask more than one question at a time

Session limit: Default 5 ChDRs per session. User can say "done" to exit early.

For each ChDR:

markdown
## ChDR-{ID}: {Title}

**Status**: {status}
**Issue Links**: {links or "none"}
**Commits**: {sha list}

### Current Content

**Context**:
{context}

**Decision** (confidence: {level}):
{decision}

**Consequences**:
{consequences}

**Evidence**:
{evidence}

### Choose Action

| Option | Action |
|---|---|
| A | **Accept** — Approve for promotion to memory |
| B | **Reject** — Decline with reason |
| C | **Defer** — Skip for now, keep pending |
| D | **Accept all remaining** — Accept this ChDR and all pending ChDRs without further review |

Reply with your choice (A/B/C/D).

Wait for user input before proceeding.

Action A: Accept

Update status to ### Status: **Accepted**. Add clarification metadata:

markdown
### Clarification

- **Date**: [YYYY-MM-DD]
- **Action**: Accepted
- **Rationale**: [summary of review]
Action D: Accept All Remaining

Accept the current ChDR (Action A), then iterate remaining pending ChDRs marking each ### Status: **Accepted** with bulk metadata. Skip per-ChDR presentation. Proceed to Phase 6.

Action B: Reject

Ask for reason:

markdown
### Decision: Reject

| Option | Reason |
|---|---|
| A | Decision was reversed (later reverted) |
| B | Inferred rationale unsupported by evidence |
| C | Project-specific / not worth recording |
| D | Duplicate of an existing ChDR or ADR |

Reply with your choice.

Update status to ### Status: **Rejected** with reason.

Action C: Defer

Keep status as-is. Add note:

markdown
### Clarification

- **Date**: [YYYY-MM-DD]
- **Action**: Deferred
- **Reason**: [need more context / waiting on team / low priority]
Phase 5: Update ChDR Files

After EACH ChDR interaction, immediately update the file. Do not batch at the end.

Phase 6: Regenerate Index

Regenerate {REPO_ROOT}/.adlc/drafts/chdr/chdr.md by listing all ChDR-*.md files and building the markdown table from single-line fields (### Status:, ### Date:, ### Issue Links:, ### Commits:, ### Descriptor:).

Phase 7: Summary
markdown
## Change-Clarify Summary

**ChDRs Reviewed**: N
**Accepted**: N
**Rejected**: N
**Deferred**: N

### Accepted (Ready for Promotion)

| ChDR | Title |
|---|---|
| ChDR-001 | [Title] |

### Rejected

| ChDR | Reason |
|---|---|
| ChDR-003 | Decision was reversed (later reverted) |

### Deferred

| ChDR | Title |
|---|---|
| ChDR-004 | [Title] |

### Next Steps

1. **Accepted**: Run `/change-publish` to promote to `docs/adlc/memory/chdr/`
2. **Deferred**: will appear in next clarify session
3. **Remaining**: run `/change-clarify` again to continue
Key Rules
One-at-a-Time
  • Present exactly ONE ChDR per response
  • Ask exactly ONE question per response
  • Wait for user input before proceeding
Immediate Writes
  • Update ChDR file after each decision
  • Regenerate index after session ends
No Auto-Approval
  • Never accept or reject without explicit user choice
  • Do not assume user preference
Provenance Is the Gate
  • A Decision claim without SHA/URL provenance is a poisoning risk — reject or require evidence before accepting
  • LOW-confidence decisions are acceptable to accept if evidence is solid; HIGH-confidence with no evidence is not
Workflow Guidance & Transitions
After /change-clarify

If any ChDRs were Accepted, handoff to /change-publish:

json
{
  "command": "clarify",
  "accepted": ["ChDR-001", "ChDR-002"],
  "rejected": ["ChDR-003"],
  "deferred": ["ChDR-004"]
}
Complete Clarify Flow
text
[Pending ChDRs exist]
    ↓
/change-clarify
    ↓
[One ChDR at a time] → Accept / Reject / Defer
    ↓
[Run /change-publish] → Promote accepted ChDRs to docs/adlc/memory/chdr/

Next Steps

After accepting ChDRs, run /change-publish to promote them to project memory and regenerate the boot-facing chdr.md index.

Verification

  • All reviewed ChDR files updated with new status and clarification metadata.
  • chdr.md drafts index regenerated.
  • Accepted ChDRs are ready for /change-publish.
  • No ChDRs were auto-accepted or auto-rejected without user input.
  • Accepted ChDRs all have provenance on Decision claims.

Context

$ARGUMENTS

© 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

SKILL.md and 2 other files (scripts) in skills/change/change-clarify of tikalk/adlc-team-skills.

  • SKILL.md
  • scripts/bash/setup-change-clarify.sh
  • scripts/powershell/setup-change-clarify.ps1

Open the folder on GitHubat commit 2dbed36

Compare with similar skills

Change Clarify 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 Clarify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Change Clarify this skilltikalk/adlc-team-skills141—~2.9kAutomated safety check: PassMIT
Commit Context Lookuprohitg00/agentmemory29k—~522Automated safety check: PassApache-2.0
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills21k—~1.9kAutomated safety check: PassMIT
Beads Task Memorygastownhall/beads28k—~1.2kAutomated safety check: PassMIT
Ownmemgrpcer/ownmem423—~593Automated safety check: PassApache-2.0
Keep The Whyoliver-zehentleitner/keep-the-why201—~9.8kAutomated safety check: PassMIT

Similar skills

  • Commit Context Lookup

    rohitg00/agentmemory

    Traces a file, function or line back to the agent session behind its current commit, using git blame and a memory lookup, and reports only what the records show.

    29k GitHub stars~522 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Neat-Freak Knowledge Closeout

    KKKKhazix/khazix-skills

    Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.

    21k GitHub stars~1.9k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed

  • Beads Task Memory

    gastownhall/beads

    Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.

    28k GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Ownmem

    grpcer/ownmem

    Recall this repository's OwnMem local memory before changing code, and keep it healthy.

    423 GitHub stars~593 tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed

  • Keep The Why

    oliver-zehentleitner/keep-the-why

    In a project with a .keep-the-why, or asked about it or to set one up (never offered or named otherwise) - extract and preserve the reasoning code cannot explain - decisions, rejected alternatives…

    201 GitHub stars~9.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Lpm Memory

    gug007/lpm

    Shared project memory for AI coding agents: save or recall work-session logs in ~/.lpm/memory/<project/<session.md so another agent CLI (Claude Code, Codex, Gemini) or a future session can continue…

    152 GitHub stars~1.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from tikalk/adlc-team-skills

All 44 skills in this repo

  • Workspace

    tikalk/adlc-team-skills

    A skill your agent uses when coordinating a multi-repo workspace — init the .adlc/ structure, discover and link child repos as submodules, or audit workspace health (branch, dirty, unpushed, SHA…

    141 GitHub starsUsed in 1 repo~3.7k tokens
    Auto-check passed

  • 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 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 Clarify

What does Change Clarify do?

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…. Change Clarify is an agent skill from tikalk/adlc-team-skills. Use when reviewing, accepting, rejecting, or deferring ChDRs mined by change-init, validating inferred decisions against their git and issue evidence before promotion to project memory.

When should I use Change Clarify?

Change Clarify fits situations like: deferring ChDRs mined by change-init; validating inferred decisions against their git and issue evidence before promotion to project memory.

How do I install Change Clarify in Claude Code?

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

How do I install Change Clarify in Codex?

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

Can I use Change Clarify 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-clarify -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-clarify, .gemini/skills/change-clarify, .github/skills/change-clarify and .opencode/skills/change-clarify in your project.

What does Change Clarify need to run?

Going by SKILL.md and its folder, Change Clarify needs a shell and PowerShell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell; PowerShell.

Does Change Clarify access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Change Clarify 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Change Clarify use?

Change Clarify 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 Clarify use?

About 2.9k tokens (SKILL.md is roughly 11k 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 Clarify?

Skills that share tags, products or a category with Change Clarify: Commit Context Lookup (rohitg00/agentmemory, 29k stars), Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), Beads Task Memory (gastownhall/beads, 28k stars) and Ownmem (grpcer/ownmem, 423 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Change Clarify?

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.