aicp-tracker 1.3.9 → 1.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,10 +1,10 @@
|
|
|
1
|
-
# AI
|
|
1
|
+
# AI Code Pulse Tracker
|
|
2
2
|
|
|
3
3
|
A lightweight background daemon that tracks your Claude Code AI usage and sends it
|
|
4
4
|
to your team's analytics backend — so you always know how many tokens your engineering
|
|
5
5
|
work actually consumes and what it costs.
|
|
6
6
|
|
|
7
|
-
[AI
|
|
7
|
+
[AI Code Pulse](https://marketplace.atlassian.com/apps/3166628045) is an AI usage analytics dashboard inside Jira that tracks Claude Code usage alongside rework rate and PR cycle time. It analyzes token consumption, cost, model usage, and cache efficiency, and correlates these signals with engineering activity such as code rework across commits and pull requests, as well as repositories, files, authors, epics, and Jira tasks, to provide visibility into development efficiency and the impact of AI-assisted workflows.
|
|
8
8
|
|
|
9
9
|
The platform helps engineering teams understand:
|
|
10
10
|
- AI usage and costs
|
|
@@ -14,7 +14,7 @@ The platform helps engineering teams understand:
|
|
|
14
14
|
- Code rework and churn
|
|
15
15
|
- Pull request lifecycle metrics
|
|
16
16
|
|
|
17
|
-
AI
|
|
17
|
+
AI Code Pulse correlates Claude Code activity with commits, repositories, pull requests, Jira issues, epics, and engineering workflows to provide visibility into how AI tools are used across the organization.
|
|
18
18
|
|
|
19
19
|
## Quick start
|
|
20
20
|
|