skills.rest
cbemister
cbemisterCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

track-progress

Log completed development work into changelogs and progress dashboards.

Updated Feb 4, 2026
Search Tags:#automation#changelog#initiatives#progress#git-history#dev-workflow#track-progress
One-click install
npx skills add https://github.com/cbemister/claude-code --skill track-progress
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: track-progress
Source: https://github.com/cbemister/claude-code/tree/main/.claude/skills/track-progress
Command: npx skills add https://github.com/cbemister/claude-code --skill track-progress

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the recording of completed development work into a changelog and progress dashboards, ensuring visibility and alignment across releases and initiatives.

Core Features & Use Cases

  • Changelog updates: generates user-facing changelog entries when features are completed.
  • Progress tracking: tracks initiative progress in a centralized view, accessible via management dashboards.
  • Catch-up and manual entries: can scan git history to generate entries or accept manual input for precise updates.

Quick Start

After finishing a feature, run the track-progress skill to update the changelog and progress dashboards.

  • Catchup mode: npx tsx database/track-progress.ts --catchup
  • Manual entry: npx tsx database/track-progress.ts --title "Feature Name" --desc "Brief description" --items "item1,item2" --category feature

Frequently Asked Questions about track-progress

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically generate a changelog from git history?▼

You can automatically generate a changelog from git history by running the track-progress script in catchup mode, which scans completed commits and logs them into your changelog and progress dashboards.

What's the best way to track feature development progress across local and production databases?▼

To track feature development progress across environments, run the track-progress script in a Node.js or TypeScript environment configured with DATABASE_URL_LOCAL and DATABASE_URL_NEON to record updates to centralized dashboards.

Can I manually add a completed feature to a changelog instead of scanning git commits?▼

Yes, you can manually add completed features by running the track-progress script with specific arguments like --title, --desc, --items, and --category to input precise updates directly into the changelog.

Do I need a specific database setup to log development work automatically?▼

You need a Node.js or TypeScript environment with configured DATABASE_URL_LOCAL and DATABASE_URL_NEON environment variables to successfully route and store automated git-history entries or manual logs.

How does automated progress tracking improve visibility for release management?▼

Automated progress tracking improves release visibility by logging completed development work into centralized dashboards and user-facing changelogs, ensuring team alignment across ongoing initiatives without manual reporting.

Related Skills

Explore More Software Engineering Skills→
AsmayaseenAsmayaseen
2

neon-postgres

Connect serverless apps to Neon PostgreSQL using HTTP and pool modes.

Community
Intermediate
ccfccf

changelog-generator

Generate user-facing changelogs from Git commits with categorized release notes.

Community
Intermediate
oldwombatoldwombat

neon-postgres

Configure and optimize Neon Serverless Postgres workflows for scalable apps.

Community
Advanced
paultyngpaultyng
9

ship-it

Automate Git pre-commit checks, changelog generation, and GitHub pull request updates.

Community
Advanced