此内容尚未提供您的语言版本,正在以英文显示。

Tc Tracker

技能已验证活跃

Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init/create/update/status/resume/close/export workflows for structured code change documentation.

目的

To provide a rigorous and auditable system for tracking technical changes throughout their lifecycle, ensuring clarity, consistency, and seamless handoffs between AI sessions.

功能

Structured JSON records for technical changes
Enforced state machine with clear transitions
Append-only revision history
Session handoff format for AI continuity
Local file storage and validation

使用场景

Tracking code changes with an audit trail
Managing the lifecycle of technical changes
Handoff in-progress work between AI sessions
Generating structured release notes
Onboarding new projects with retroactive documentation

非目标

Generating changelogs solely from git history
Tracking generic tech debt items
Documenting trivial changes (typos, formatting)

安装

请先添加 Marketplace

/plugin marketplace add alirezarezvani/claude-skills

/plugin install engineering@claude-code-skills

质量评分

已验证

99 /100

1 day ago 分析

信任信号

最近提交1 day ago

GitHub 所有者 alirezarezvani

星标14.6k

许可证MIT

网站alirezarezvani.medium.com

状态

查看源代码

类似扩展

Teach Guidance

100

Guide a person in becoming a better teacher and explainer. AI coaches content structuring, audience calibration, explanation clarity, Socratic questioning technique, feedback interpretation, and reflective practice for technical presentations, documentation, and mentoring. Use when a person needs to present technical content and wants preparation coaching, wants to write better documentation or tutorials, struggles to explain concepts across expertise levels, is mentoring a colleague, or is preparing for a talk or knowledge-sharing session.

技能

pjt222

Prepare Inspection Readiness

100

Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.

技能

pjt222