Orca CLI
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity
Install Technical Change Tracker
$ npx skills add sickn33/agentic-awesome-skills --skill technical-change-tracker -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills technical-change-tracker --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/technical-change-tracker .claude/skills/technical-change-tracker && rm -rf skills-srcUse ~/.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/
Install the "technical-change-tracker" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/technical-change-tracker into .claude/skills/technical-change-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-change-tracker", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/technical-change-trackerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sickn33/agentic-awesome-skills --skill technical-change-tracker -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills technical-change-tracker --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/technical-change-tracker .agents/skills/technical-change-tracker && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "technical-change-tracker" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/technical-change-tracker into .agents/skills/technical-change-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-change-tracker", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill technical-change-tracker -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills technical-change-tracker --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/technical-change-tracker .cursor/skills/technical-change-tracker && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "technical-change-tracker" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/technical-change-tracker into .cursor/skills/technical-change-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-change-tracker", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/technical-change-tracker--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sickn33/agentic-awesome-skills --skill technical-change-tracker -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills technical-change-tracker --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/technical-change-tracker .gemini/skills/technical-change-tracker && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "technical-change-tracker" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/technical-change-tracker into .gemini/skills/technical-change-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-change-tracker", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sickn33/agentic-awesome-skills technical-change-trackerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sickn33/agentic-awesome-skills --skill technical-change-tracker -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/technical-change-tracker .github/skills/technical-change-tracker && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "technical-change-tracker" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/technical-change-tracker into .github/skills/technical-change-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-change-tracker", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill technical-change-tracker -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills technical-change-tracker --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/technical-change-tracker .opencode/skills/technical-change-tracker && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "technical-change-tracker" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/technical-change-tracker into .opencode/skills/technical-change-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-change-tracker", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
technical-change-tracker- GitHub stars
- 47k
- Used in
- 2 other repos
- Token cost
- ~559 tokens
- SKILL.md length
- 228 words
- Files
- 1
- Skills in repo
- 1,354
- Repo updated
- First seen
- Licence
- MIT
At a glance
Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity
- Tasks that involve Session handoff
- SKILL.md covers Overview, When to Use This Skill, How It Works and Features, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Technical Change Tracker is an agent skill from sickn33/agentic-awesome-skills. Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity
Its SKILL.md is about 560 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 Agent Workflows, covering Session handoff. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
When your agent uses it
- Tasks that involve Session handoff
Example prompts
- “/technical-change-tracker”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit ec02547. 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.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
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
Technical Change Tracker loads about 559 tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 228 words of instructions outside code blocks.
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 sickn33/agentic-awesome-skills at commit ec02547, republished under its MIT licence (© sickn33). 228 words, ~559 tokens.
Download SKILL.mdSave it as
.claude/skills/technical-change-tracker/SKILL.md (or your agent's skills folder).- name
- technical-change-tracker
- description
- Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity
- category
- development
- risk
- safe
- source
- community
- source_repo
- Elkidogz/technical-change-skill
- source_type
- community
- date_added
- 2026-04-05
- author
- Elkidogz
- tags
- change-tracking, session-handoff, documentation, accessibility, state-machine
- tools
- claude, cursor, gemini, codex
Technical Change Tracker
Overview
Track every code change with structured JSON records and accessible HTML output. Ensures AI bot sessions can resume seamlessly when previous sessions expire or are abandoned.
When to Use This Skill
- Use when you need structured change tracking across AI coding sessions
- Use when a bot session expires mid-task and the next session needs full context to resume
- Use when onboarding a project with undocumented change history
How It Works
State Machine
planned -> in_progress -> implemented -> tested -> deployed
|
+-> blockedCommands
/tc init | /tc create | /tc update | /tc status | /tc resume | /tc close | /tc export | /tc dashboard | /tc retro
Session Handoff
Each TC stores: progress summary, next steps, blockers, key context, and files in progress — so the next bot session picks up exactly where the last left off.
Non-Blocking
TC bookkeeping runs via background subagents. Never interrupts coding work.
Features
- Structured JSON records with append-only revision history
- Test cases with log snippet evidence
- WCAG AA+ accessible HTML output (dark theme, rem-based fonts)
- CSS-only dashboard with status filters
- Python stdlib only — zero external dependencies
- Retroactive bulk creation from git history via
/tc retro
Full Repository
https://github.com/Elkidogz/technical-change-skill — MIT License
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
© sickn33, 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/technical-change-tracker of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit ec02547
Used in 2 other repositories
We found 8 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
- lingxling/awesome-skills-cnantigravity-awesome-skills/skills/technical-change-trackerantigravity-awesome-skills/plugins/agentic-awesome-skills/skills/technical-change-tracker+1 more
- henryalouf/ruflow.agents/skills/technical-change-trackersrc/antigravity-awesome-skills/plugins/antigravity-awesome-skills/skills/technical-change-tracker+1 more
Compare with similar skills
Technical Change Tracker 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Technical Change Tracker this skillsickn33/agentic-awesome-skills | 47k | 2 repos | ~559 | Automated safety check: Pass | MIT | |
| Orca CLIstablyai/orca | 87k | 2 repos | ~593 | Automated safety check: Pass | MIT | |
| Coding Agent Session Findercode-yeongyu/oh-my-openagent | 70k | 1 repos | ~2.8k | Automated safety check: Pass | Custom licence | |
| Beads Task Memorygastownhall/beads | 28k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Session History Searchslopus/happy | 24k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Paseo Agent Handoffgetpaseo/paseo | 20k | 1 repos | ~606 | Automated safety check: Pass | Custom licence |
Similar skills
Coding Agent Session Finder
code-yeongyu/oh-my-openagent
Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.
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.
Session History Search
slopus/happy
Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.
Paseo Agent Handoff
getpaseo/paseo
Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.
Memori Long-Term Memory
MemoriLabs/Memori
Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.
More from sickn33/agentic-awesome-skills
All 1,354 skills in this repoLiuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Find Complementary Founders
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Content Creator
sickn33/agentic-awesome-skills
Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.
Related
Categories
Questions about Technical Change Tracker
What does Technical Change Tracker do?
Track code changes with structured JSON records, state machine enforcement, and AI session handoff for bot continuity. Technical Change Tracker is an agent skill from sickn33/agentic-awesome-skills.
When should I use Technical Change Tracker?
Technical Change Tracker fits situations like: tasks that involve Session handoff.
How do I install Technical Change Tracker in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill technical-change-tracker -a claude-code`. Or copy the skill folder (skills/technical-change-tracker in sickn33/agentic-awesome-skills) into .claude/skills/technical-change-tracker in your project. Claude Code loads it when a task matches its description.
How do I install Technical Change Tracker in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill technical-change-tracker -a codex`. Or copy the skill folder (skills/technical-change-tracker in sickn33/agentic-awesome-skills) into .agents/skills/technical-change-tracker in your project. Codex loads it when a task matches its description.
Can I use Technical Change Tracker 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 sickn33/agentic-awesome-skills --skill technical-change-tracker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/technical-change-tracker, .gemini/skills/technical-change-tracker, .github/skills/technical-change-tracker and .opencode/skills/technical-change-tracker in your project.
What does Technical Change Tracker need to run?
SKILL.md names no scripts, command-line tools or credentials: Technical Change Tracker is instructions for the agent only. Our summary lists: Python 3.
Does Technical Change Tracker access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Technical Change Tracker 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 Technical Change Tracker use?
Technical Change Tracker 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 Technical Change Tracker use?
About 559 tokens (SKILL.md is roughly 2.2k 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 Technical Change Tracker?
Skills that share tags, products or a category with Technical Change Tracker: Orca CLI (stablyai/orca, 87k stars), Coding Agent Session Finder (code-yeongyu/oh-my-openagent, 70k stars), Beads Task Memory (gastownhall/beads, 28k stars) and Session History Search (slopus/happy, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Technical Change Tracker?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,343 GitHub stars. The repository holds 1,354 skills in this directory. The repository was last updated on October 7, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.