Metricas

Use to track delivery/flow metrics — Lead Time (time to production) and Throughput (items completed per cycle) — the maturity of Continuous Delivery vs Continuous Deployment, and code quality (coverage and static analysis) as a traceable trend. Reads git/Jira/CI and the quality artifacts when an MCP is connected and updates docs/engineering/metrics.md. Trigger with /metricas.

100 stars 27 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add adriannoes/awesome-agentic-ai --skill metricas
Manual install
git clone --depth 1 https://github.com/adriannoes/awesome-agentic-ai.git /tmp/awesome-agentic-ai
mkdir -p ~/.claude/skills
cp -r /tmp/awesome-agentic-ai/cursor-claude-codex/skills/igoruehara-spec-driven/skills/metricas ~/.claude/skills/metricas

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

> **Translation note:** Originally authored in Portuguese (pt-BR) by Igor Uehara ([igoruehara/spec-driven](https://github.com/igoruehara/spec-driven), MIT). Translated to English by this hub to keep the repository language consistent. Original content unchanged in meaning; see the upstream repo for the pt-BR source.

# Skill: Delivery metrics (Lead Time · Throughput · CD)

Tracks the health of the delivery flow. **Idempotent**: re-running recalculates the period.
Principle: use it to **find bottlenecks**, not to rank people (do not encourage gaming).

## Define the period
Ask (`AskUserQuestion`) for the cycle (sprint / week / month) and the date window.

## 1. Lead Time — how long until production
Time from **"started" → "in production"** per item.
- **Start** (use whatever exists): date of the spec/STATE, issue creation (Jira), or the 1st commit.
- **End:** deploy to prod — tag/release, CI/CD log, or Jira "done" status.
- Compute per item and the aggregate: **median** and **p85** (more robust than the mean). Break it down by
  tier/type (feature/bug) if useful.

## 2. Throughput — items completed in the cycle
Number of items that reached **"done"/prod** in the period (stories, bugs, tasks).
- Sources: `specs/` marked as implemented, merged PRs, closed issues (Jira), deploys.
- Report the **absolute number** per cycle and the **trend** (↑ / → / ↓ vs the previous cycle).

## 3. Continuous Delivery vs Continuous Deployment
Assess where the team stands and the gap:
Read the full skill on GitHub

Details

Skill name
metricas
Path
cursor-claude-codex/skills/igoruehara-spec-driven/skills/metricas/SKILL.md
License
MIT
Repo updated
2 November 2026

FAQ

What does the Metricas skill do?

Use to track delivery/flow metrics — Lead Time (time to production) and Throughput (items completed per cycle) — the maturity of Continuous Delivery vs Continuous Deployment, and code quality (coverage and static analysis) as a traceable trend. Reads git/Jira/CI and the quality artifacts when an MCP is connected and updates docs/engineering/metrics.md. Trigger with /metricas.

How do I install the Metricas skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add adriannoes/awesome-agentic-ai --skill metricas. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Metricas popular?

It lives in adriannoes/awesome-agentic-ai, which has 100 GitHub stars and 27 forks, and is included in 2 curated skill lists.

Related skills

Browserstack

100

adriannoes/awesome-agentic-ai

Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".

Testing & QAIn 2 lists27

Coverage

100

adriannoes/awesome-agentic-ai

Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".

Testing & QAIn 2 lists27

Fix

100

adriannoes/awesome-agentic-ai

Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".

Testing & QAIn 2 lists27

Paw Mkt PR

118

pawbytes/skill-suites

Media relations, press releases, journalist outreach, and crisis comms. Use when the user requests 'press release', 'media outreach', 'journalist pitch', 'crisis comms', 'reputation management', or 'PR strategy'.

Git & Code Review23

Integrating Sast Into Github Actions Pipeline

100

adriannoes/awesome-agentic-ai

This skill covers integrating Static Application Security Testing (SAST) tools—CodeQL and Semgrep—into GitHub Actions CI/CD pipelines. It addresses configuring automated code scanning on pull requests and pushes, tuning rules to reduce false positives, uploading SARIF results to GitHub Advanced Security, and establishing quality gates that block merges when high-severity vulnerabilities are detected.

Git & Code ReviewIn 2 lists27

Paw Tools Release

118

pawbytes/skill-suites

Automates software releases from version bump to GitHub release. Use when the user requests to 'create a release', 'cut a release', 'publish a new version', or 'prepare a release'.

Git & Code Review23

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.