Overview
Master score
86 / 100
Quality, Speed and Consumption weigh a third each: each is the mean of the tabs scored in it, and the master is the mean of the 3 categories, over 12 measured tabs of 13. A tab is the mean of its categories. 144 of 156 metrics measured; one not measured is shown, never scored as 0.
Quality
91
12 of 13 tabs measured
Speed
74
11 of 13 tabs measured
Consumption
94
9 of 12 tabs measured
156 metrics
119 meet15 near10 miss12 not measuredWork queue
Every metric near or missing its goal, across tabs and Quality, Speed and Consumption, ranked by the master points it adds when it meets its goal.
- InsightsOldest leftover branch189 hoursgoal ≤ 24 · +3 points
- IssuesRunner minutes per issue, the latest fix72 minutesgoal ≤ 60 · +1.9 points
- IssuesOldest open issue8.7 daysgoal ≤ 2 · +1.5 points
- SecurityOldest open alert8.5 daysgoal ≤ 7 · +1.5 points
- ProjectsOldest card in progress7.9 daysgoal ≤ 7 · +0.8 points
- ProjectsCards read at a glance52.4%goal ≥ 100 · +0.6 points
- PRsLongest wait after all green1,962 minutesgoal ≤ 30 · +0.5 points
- PRsOpen PRs now22 PRsgoal ≤ 10 · +0.5 points
- IssuesIssues with an area label74.4%goal ≥ 100 · +0.3 points
- ProjectsIn progress, no open PR1 cardsgoal ≤ 0 · +0.3 points
- PRsOldest open PR2.2 daysgoal ≤ 1 · +0.3 points
- PRsLatest PR's hours to merge10.8 hoursgoal ≤ 4 · +0.3 points
- DependabotOpen dependency PRs2 PRsgoal ≤ 1 · +0.3 points
- DependabotDirect dependencies on the latest allowed60%goal ≥ 100 · +0.2 points
- DocsContent-lint WARN in docs6 findingsgoal ≤ 0 · +0.2 points
- DependabotAdopting repos within the cooldown of the newest tag0%goal ≥ 100 · +0.2 points
- DocsDocs with an interactive element70%goal ≥ 100 · +0.2 points
- IssuesParked issues2 issuesgoal ≤ 0 · +0.2 points
- IssuesOpen bugs1 bugsgoal ≤ 0 · +0.2 points
- IssuesCards with a visual95%goal ≥ 100 · +0.2 points
- DocsNamed repo paths that are missing2 pathsgoal ≤ 0 · +0.1 points
- PRsFixed after the first review40%goal ≤ 25 · +0.1 points
- DocsFolders with README or map row90%goal ≥ 100 · +0.1 points
- DependabotActions pinned to the latest allowed90.9%goal ≥ 100 · +0.1 points
- PagesReading grade, hardest page9.3 gradegoal ≤ 9 · +0.1 points
Front peak: qualityBack peak: speedSnow: above 80
Scoreboard
| Review | ||||
|---|---|---|---|---|
| Code | 10013 of 15 | 1001 of 1 | 0 | – |
| Documentation | 7713 of 13 | 1001 of 1 | 2 | – |
| Issues | 729 of 9 | 502 of 2 | 2 | – |
| Pull requests | 9510 of 10 | 506 of 6 | 2 | – |
| Discussions | –0 of 0 | –0 of 0 | 0 | – |
| Actions | 1009 of 9 | 1004 of 4 | 0 | – |
| Projects | 705 of 6 | 752 of 2 | 1 | – |
| Security and quality | 1002 of 2 | 501 of 1 | 0 | – |
| Dependabot | 7912 of 12 | 926 of 6 | 2 | – |
| Scanning | 1004 of 4 | –0 of 0 | 0 | – |
| Insights | 1001 of 1 | 01 of 1 | 1 | – |
| Settings | 1005 of 7 | 1001 of 2 | 0 | – |
| Pages | 9511 of 13 | 1008 of 8 | 0 | – |
Not measured
12
- CodeCode qualityneeds an admin token; refreshed by a --local collect run
- CodeOpen code quality findingsneeds an admin token; refreshed by a --local collect run
- ProjectsRunner minutes per pull request, the latest card#96, the latest merged pull request on the latest card, opened 2026-11-13 14:47 UTC, before 2026-11-13 16:26 UTC, where the runs read stop covering every workflow
- ProjectsBoard workflows ongh api failed: You do not have permission to access workflows
- DependabotCI minutes on the latest dependency PRno merged PR labeled dependencies yet
- SettingsProtections missinga ruleset's bypass list is hidden from this token: needs an admin token; refreshed by a --local collect run
- SettingsGeneral settings off standardgh api repos answered without allow_squash_merge: needs an admin token; refreshed by a --local collect run
- SettingsSettings that bill past the plana public repo is not billed for Actions cache or a Copilot review, so nothing here can bill it
- SettingsAge of the admin readingsno signed-in run is recorded yet: run collect.mjs --local
- PagesLatest failure's time to restorenone of the last 10 deploys failed, so there is nothing to restore
- PagesPages visibility privatea public repo publishes a public Pages site: private Pages needs a private repo on GitHub Enterprise Cloud
- PagesForm page KiB, heaviest formparams.form_pages names no form page
Code
Quality
100
13 of 15 measured
Speed
100
1 of 1 measured
Consumption
100
3 of 3 measured
Ideal state
The least code that does the job: every part small, used, named, explained and drawn, fast to run and cheap for an agent to read.
| Part | Ideal | Set up |
|---|---|---|
| Size | No function past complexity 10 or 50 lines, and no file past 300 lines | Split the worst function first; the tab lists every item over a limit |
| Dead and stale code | No unused file, export, package or function, and no comment naming a file that is gone | knip reads JavaScript, Python's ast reads Python; delete what they list |
| Comments | Every shared function says what it does on the line where it starts | A header comment in JavaScript, a docstring in Python |
| Names | Every file and folder follows the naming rule of its folder | Name the rules once in the repo's targets; the tab lists each name that breaks one |
| Structure | Imports run one way, with no cycle between files | Move the shared piece to a file both sides import |
| Visual | Every code area is drawn in a table or a diagram a reader lands on | A table row or a Mermaid block in a README, or in a doc it links |
| Speed | The guard judges a command within a tenth of a second | Time it where sessions run; keep imports and rule loading off the hot path |
| Tokens | Every file fits one Read call and every area fits one context window | Split a file past 25,000 tokens and an area past 200K |
20 sources, newest 2026-11-10
- Claude Code Docs: Tools reference 2026-11-10
- Claude Code Docs: Best practices for Claude Code 2026-11-10
- Claude Code Docs: Manage costs effectively 2026-11-10
- Claude Docs: Context windows 2026-11-10
- Anthropic: Effective context engineering for AI agents 2025-09-29
- GitHub Docs: Code Quality metrics and scores reference 2026-11-10
- GitHub Docs: Best practices for repositories 2026-11-10
- Microsoft Learn: Code metrics, cyclomatic complexity 2026-10-20
- Microsoft Learn: Architecture strategies for optimizing code and infrastructure 2025-10-30
- Microsoft Engineering Fundamentals Playbook: Code Reviews 2024-08-26
- PEP 257: Docstring Conventions 2024-04-17
- PEP 8: Style Guide for Python Code 2025-04-04
- ESLint: max-lines 2026-11-10
- ESLint: max-lines-per-function 2026-11-10
- Google Engineering Practices: What to look for in a code review 2026-11-04
- Nielsen Norman Group: Response Times, The 3 Important Limits 1993-01-01
- Node.js v26 docs: Modules, CommonJS modules, Cycles 2026-11-10
- Microsoft Learn: How code metrics help identify risks 2026-10-20
- GitHub Docs: About the repository README file 2026-11-10
- GitHub Docs: Creating diagrams 2026-11-10
Quality
No function past complexity 10 or 50 lines, no file past 300, nothing unused or uncommented, no import cycle, every area drawn from its README.
Size100
Files over 300 lines0 filesgoal ≤ 0
Files so long that they are hard to read in one sitting, in every language, stylesheets included.
.ts, .mjs, .astro, .css, .py and .sh files over 300 code lines read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: no file over the limit. The limit, params.limits.file_lines (300), is the default of ESLint's max-lines rule (eslint.org/docs/latest/rules/max-lines)
Functions over 50 lines0 functionsgoal ≤ 0
Pieces of code too long to understand at a glance.
TypeScript compiler API and Python's ast over 18 of 18 .py file(s), functions over 50 code lines read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: no function over the limit. The limit, params.limits.function_lines (50), is the default of ESLint's max-lines-per-function rule (eslint.org/docs/latest/rules/max-lines-per-function)
Functions over complexity 100 functionsgoal ≤ 0
Pieces of code with so many branches that they are hard to test and change.
TypeScript compiler API and Python's ast over 18 of 18 .py file(s), McCabe complexity over 10 read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: no function over the limit. The limit, params.limits.complexity (10), is McCabe's (A Complexity Measure, IEEE Transactions on Software Engineering, 1976)
Dead code100
Unused files (knip)0 filesgoal ≤ 0
Files nothing uses. They can be deleted.
knip --reporter json (the repo's knip config) read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: an unused file is code to read and keep that does nothing. Unused or dead code is a maintainability finding (GitHub Docs, Code Quality metrics and scores reference, docs.github.com/en/code-security/reference/code-quality/metrics-and-ratings, read 2026-11-10); zero is a Git Crafter default
Unused exports (knip)0 exportsgoal ≤ 0
Code offered to other files that no file uses.
knip --reporter json (the repo's knip config) read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: an export no caller needs is dead code, a maintainability finding (GitHub Docs, Code Quality metrics and scores reference, docs.github.com/en/code-security/reference/code-quality/metrics-and-ratings, read 2026-11-10); zero is a Git Crafter default
Unused dependencies (knip)0 dependenciesgoal ≤ 0
Outside packages installed but never used.
knip --reporter json (the repo's knip config) read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: an unused package costs install time and supply-chain risk for nothing; unused code is a maintainability finding (GitHub Docs, Code Quality metrics and scores reference, docs.github.com/en/code-security/reference/code-quality/metrics-and-ratings, read 2026-11-10); zero is a Git Crafter default
Unused Python functions0 functionsgoal ≤ 0
Python functions that no code or test in the code folders calls or names. They can be deleted.
top-level functions of .py files that no .py file in the areas, tests included, reads, imports or names and Python's ast over 18 of 18 .py file(s) read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: an unused function is code to read and keep that does nothing. Unused or dead code is a maintainability finding (GitHub Docs, Code Quality metrics and scores reference, read 2026-11-10); knip reads no Python, so this metric does
Drift100
References to deleted files0 referencesgoal ≤ 0
Comments and strings that point at files which were deleted or moved.
comments and strings naming files that git log shows were committed and are now gone read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal, our own inference: a reference to a deleted file sends a reader, or Claude, to a dead end. An agent keeps file paths as references and loads each file when it needs it (Anthropic, Effective context engineering for AI agents, anthropic.com/research/effective-context-engineering-for-ai-agents, 2025-09-29, read 2026-11-10)
Comments that help Claude100
Shared functions with a header comment100%goal ≥ 100
Functions other files can call that say what they do in a comment or docstring right at their start.
| tools | 100% | |
|---|---|---|
| quality | 100% | |
| ciquality/collectors/ | 100% | |
| codequality/collectors/ | 100% | |
| docsquality/collectors/ | 100% | |
| githubquality/collectors/ | 100% | |
| insightsquality/collectors/ | 100% | |
| libquality/collectors/ | 100% | |
| settingsquality/collectors/ | 100% | |
| sitequality/collectors/ | 100% | |
| testsquality/collectors/ | 100% | |
| toolsquality/collectors/ | 100% |
12 of 15 shown
exported functions with a comment on the line above, and public Python functions with a docstring or one: TypeScript compiler API and Python's ast over 18 of 18 .py file(s); 834 of 834 read 2026-11-21 13:37 UTC
Goal: Git Crafter's own goal: every shared function says what it does, as all functions a module exports should have docstrings (PEP 257, peps.python.org/pep-0257, last modified 2024-04-17, read 2026-11-10); near is the template's goal
Structure100
Files and folders named by convention100%goal ≥ 100
Files and folders named the way their neighbors are, so they are easy to find.
| kebab-case modules (128) | 100% | |
|---|---|---|
| kebab-case pages (14) | 100% | |
| snake_case tools (34) | 100% |
code files in the areas, and the folders that hold them, named by their folder's convention (params.naming); 176 of 176 read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: every code file and folder follows its folder's convention. No outside standard for the share; Python's own convention is short, all-lowercase module names (PEP 8, peps.python.org/pep-0008, read 2026-11-10)
Code areas drawn in a README100%goal ≥ 100
Code folders that a README, or a doc it links, shows in a table or a diagram, so a reader sees the layout.
areas named in a table row or a mermaid block of a README.md at their folder or above, or of a doc it links beside it; 16 of 16 read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: every code area is drawn where a reader lands. A README tells people about a project, and GitHub renders Mermaid diagrams in Markdown (GitHub Docs, About the repository README file, and Creating diagrams, read 2026-11-10); the share is a Git Crafter default
Import cycles0 cyclesgoal ≤ 0
Groups of files that import each other, so none of them can be read, tested or changed alone.
relative imports and re-exports (TypeScript compiler API) and sibling-module imports of .py files; groups of two or more files that import each other read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: no import cycle. In a cycle a module might not have finished executing when it is returned (Node.js v26 docs, Modules: CommonJS modules, Cycles, read 2026-11-10), and low coupling is what Microsoft's code metrics ask for (Microsoft Learn, Code metrics values, updated 2026-10-20, read 2026-11-10)
Coverage100
Line and branch coverage93.8%goal ≥ 80
The share of code lines and branches the automated tests run, together, close to how SonarQube counts coverage.
| pages lines | 95.8% | |
|---|---|---|
| pages branches | 85.6% | |
| quality lines | 96.1% | |
| quality branches | 89.3% | |
| collectors linesconfig/quality/ | 100% | |
| collectors branchesconfig/quality/ | 88.2% |
node --test --experimental-test-coverage lcov printed by verify.yml job short, run 43744847284 (2026-11-15), lines and branches together: 17306 of 18004 lines and 7796 of 8763 branches covered in pages, quality, config/quality/collectors read 2026-11-21 13:37 UTC
Goal: goal: new code test coverage of 80.0% or more, a condition of SonarQube Server 2026.5 docs, Introduction to quality gates, the built-in Sonar way gate (docs.sonarsource.com, read 2026-11-04). SonarQube coverage mixes lines and conditions, coverage = (CT + LC)/(B + EL) (SonarQube Server 2026.5 docs, Metric definitions, read 2026-11-04), so branches count beside lines. v8 counts true and false branch outcomes apart, where that formula counts true once, so the share approximates SonarQube coverage rather than matching it; the near band is a Git Crafter default
GitHub features–
Code quality–goal ≥ 1
Whether GitHub checks the repo's code for maintainability and reliability problems; on is better, even where it costs.
needs an admin token; refreshed by a --local collect run
gh api repos/SoulCraft-Org/git-crafter/code-quality/setup (state)
Goal: GitHub docs, GitHub Code Quality
Open findings–
Open code quality findings–goal ≤ 0
Maintainability and reliability problems GitHub found in the code; not counted while code quality is off.
needs an admin token; refreshed by a --local collect run
gh api repos/SoulCraft-Org/git-crafter/code-quality/findings?state=open --paginate (by rule.severity)
Goal: template goal: none open (GitHub docs, GitHub Code Quality)
Speed
The guard, which runs before every command, answers within a tenth of a second.
Engine100
Quality page collect and build in CI41 sgoal ≤ 45
Seconds the engine takes to collect and build this Quality page on a push to main, as every adopter waits.
| 2026-11-15T18:06Z 166d3a3 | 43 s | |
|---|---|---|
| 2026-11-14T04:56Z 8023bd4 | 35 s | |
| 2026-11-14T04:33Z c267bc4 | 38 s | |
| 2026-11-14T04:08Z 689a2c2 | 48 s | |
| 2026-11-14T00:52Z 70153ae | 41 s |
last 5 successful pushes to main: median seconds of the pages.yml build job's step "Git Crafter's own Quality, Speed and Consumption page" (gh api actions/runs/{id}/jobs) read 2026-11-21 13:37 UTC
Goal: Git Crafter goal (2026-11-11), set from readings: every third successful pages.yml push to main, 74 runs 2026-11-04 to 2026-11-11 (gh api actions/runs/{id}/jobs, read 2026-11-11), timed this step at 21 to 78 s, median 41 s, and its daily median rose from 26 s to 54 s. A 45 s goal holds the week's median; the median of 5 runs passed it in 28 of 70 windows. Near is twice the goal. No first-party source sets a number for this step
Consumption
Every file fits one Read call of 25,000 tokens, and every area fits a 200K-token context window.
Cost100
Runner minutes, the latest Code Quality scan2 minutesgoal ≤ 5
Billed runner minutes the latest passed run of GitHub's Code Quality scan took; lower is better
| CodeQL - Code Quality | 2 minutes |
|---|
latest: gh api actions/runs/{id}/jobs: GitHub's dynamic CodeQL - Code Quality workflow, its latest passed run, read with the security scans; billed runner minutes, summed read 2026-11-21 13:37 UTC
Goal: template goal (2026-11-13): the Code Quality scan on one change bills at most 5 runner minutes, as the security scans do, half the ten-minute build (Kent Beck, Extreme Programming Explained, 2nd edition, 2004)
Size100
Code a session reads, largest area, in tokens132K tokensgoal ≤ 200K
The largest area's code, tests included, as tokens a session loads to read that area whole.
132,293 tokens
| tools | 132,293 tokens | |
|---|---|---|
| githubquality/collectors/ | 119,146 tokens | |
| quality | 111,058 tokens | |
| codequality/collectors/ | 85,749 tokens | |
| renderquality/ | 76,768 tokens | |
| sitequality/collectors/ | 74,709 tokens | |
| ciquality/collectors/ | 66,225 tokens | |
| pages | 49,364 tokens | |
| docsquality/collectors/ | 44,429 tokens | |
| testsquality/collectors/ | 27,779 tokens | |
| toolsquality/collectors/ | 27,300 tokens | |
| settingsquality/collectors/ | 13,527 tokens |
12 of 16 shown
state: bytes of the code files in the largest area of params.areas, tests included, over params.bytes_per_token: tools read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: one area fits a 200k-token context window, the smallest Claude still serves; near is the 1M largest, and recall degrades as context grows (platform.claude.com/docs/en/build-with-claude/context-windows, read 2026-11-03). An agent keeps lightweight references and loads files just in time with its tools, so a session reads the area it works in (Anthropic, Effective context engineering for AI agents, anthropic.com/research/effective-context-engineering-for-ai-agents, 2025-09-29, read 2026-11-04)
Largest code file, in tokens22,032 tokensgoal ≤ 25,000
The biggest code file, tests included, as tokens a session loads to read it whole.
| github-more.test.mjsquality/collectors/github/ | 22,032 tokens | |
|---|---|---|
| pages-collect.test.mjstests/ | 21,296 tokens | |
| docs.test.mjsquality/collectors/docs/ | 19,159 tokens | |
| code.test.mjsquality/collectors/code/ | 18,283 tokens | |
| pages-build.test.mjstests/ | 17,842 tokens | |
| github-security.test.mjsquality/collectors/github/ | 17,643 tokens | |
| tests.test.mjsquality/collectors/tests/ | 14,886 tokens | |
| code-inputs.test.mjsquality/collectors/code/ | 14,007 tokens | |
| ci-collect.test.mjsquality/collectors/ci/ | 13,225 tokens | |
| usability.test.mjsquality/collectors/site/ | 12,555 tokens |
state: bytes of the largest code file in params.areas and params.size_extra, tests included, over params.bytes_per_token: quality/collectors/github/github-more.test.mjs read 2026-11-21 13:37 UTC
Goal: goal: one Read call returns at most 25,000 tokens by default, so a larger file is read a page at a time; near is 111,500 tokens, the 256 KB past which Read refuses a whole file, at params.bytes_per_token (2.35) bytes a token (Claude Code Docs, Tools reference, code.claude.com/docs/en/tools-reference, read 2026-11-10)
Documentation
Quality
77
13 of 13 measured
Speed
100
1 of 1 measured
Consumption
100
1 of 1 measured
Ideal state
Every fact a reader needs is present, correct and current, in short, visual, accessible docs a person finishes in two minutes and Claude loads cheaply.
15 sources, newest 2026-11-10
- GitHub Docs: About the repository README file 2026-11-10
- GitHub Docs: About community profiles for public repositories 2026-11-10
- GitHub Docs: Adding support resources to your project 2026-11-10
- GitHub Docs: Creating a default community health file 2026-11-10
- GitHub Docs: Style guide 2026-11-10
- GitHub Docs: Creating diagrams 2026-11-10
- GitHub Docs: Organizing information with collapsed sections 2026-11-10
- Microsoft Style Guide: Top 10 tips for Microsoft style and voice 2026-07-02
- Microsoft Style Guide: Scannable content 2023-06-20
- Microsoft Style Guide: Tables 2026-11-10
- Microsoft Style Guide: Alternative text 2026-04-03
- Microsoft Engineering Fundamentals Playbook: Documentation 2026-11-10
- Claude Code Docs: How Claude remembers your project 2026-11-10
- Claude Docs: Skill authoring best practices 2026-11-10
- Brysbaert, 2019: How many words do we read per minute? (Journal of Memory and Language 109) 2026-11-03
Quality
Paths, scripts and links resolve, nothing is stale, folders and community files are covered, headings and images are accessible, and docs are visual first.
Correct70
Content-lint WARN in docs6 findingsgoal ≤ 0
Likely breaks of the repo's own writing rules, in the docs those rules cover
Gap: 6 findings over goal
| docs checked | 45 docs |
|---|---|
| docs outside lint scope | 0 docs |
| THREAT-MODEL.mdtools/ | 5 findings |
| README.mdtemplates/open/ | 1 findings |
python3 tools/voice_lint.py <45 docs> read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: no content-lint warning in the docs the lint covers. Source: Microsoft Style Guide: Top 10 tips for Microsoft style and voice (prune every excess word)
Named repo paths that are missing2 pathsgoal ≤ 0
File and folder paths a doc writes in code that no longer exist in the repo
Gap: 2 paths over goal
| repo paths checked | 174 paths |
|---|---|
| templates/agents/README.md:8 templates/claude | 1 paths |
| templates/open/README.md:54 actions/attest | 1 paths |
each word of inline code and code blocks under a top-level repo entry, git-ignored paths and records skipped (a heuristic), quality/collectors/docs/docs.mjs over 45 docs (params.doc_set) read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: every path a doc names exists. Source: Microsoft Engineering Fundamentals Playbook: Documentation (an inaccurate doc names the wrong folders and settings)
Named npm scripts that are missing0 scriptsgoal ≤ 0
npm commands in a doc that run a script no package.json in the repo defines
| npm script references checked | 0 scripts |
|---|
npm run, test and start in inline code and code blocks, against package.json; with -w, that workspace alone; records skipped, quality/collectors/docs/docs.mjs over 45 docs (params.doc_set) read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: every npm script a doc names runs. Source: Microsoft Engineering Fundamentals Playbook: Documentation (inaccurate docs)
Broken relative links and anchors0 linksgoal ≤ 0
Links from one doc to another file or heading in the repo that lead nowhere
| relative links checked | 203 links |
|---|
relative markdown links and #anchors, quality/collectors/docs/docs.mjs over 45 docs (params.doc_set) read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: every relative link and anchor resolves. Source: GitHub Docs: About the repository README file (relative links)
Heading and image faults0 faultsgoal ≤ 0
Headings that skip a level or repeat, and images a screen reader cannot describe
| headings and images checked | 105 faults |
|---|
104 headings (a skipped level, a second H1, a heading repeated at its level) and 1 images (no alt text, or over 150 characters) outside code, quality/collectors/docs/docs.mjs over 45 docs (params.doc_set) read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: headings run in order with no repeat, and every image has alt text within the limit. Sources: GitHub Docs: Style guide (no header level is skipped, and each header at a level is unique); Microsoft Style Guide: Alternative text (limit the length to 150 characters)
Current100
Stale markers in docs0 markersgoal ≤ 0
Words that flag unfinished text, such as TODO or not yet, outside code
TODO, TBD, FIXME, not yet, coming soon outside code and comments, quality/collectors/docs/docs.mjs over 45 docs (params.doc_set) read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: no doc says its own text is unfinished. Source: Microsoft Engineering Fundamentals Playbook: Documentation (incomplete docs)
Dated claims older than their area0 datesgoal ≤ 0
Current as of and last verified dates set before the files the doc covers last changed
0 "current as of", "last verified" dates outside code, each against the last commit to its doc's area (params.areas), quality/collectors/docs/docs.mjs over 45 docs (params.doc_set) read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: a dated claim is at least as new as what it describes. Source: Microsoft Engineering Fundamentals Playbook: Documentation (obsolete docs)
Oldest doc lag behind its area3.1 daysgoal ≤ 7
Days the doc that trails its subject most has gone without catching up to it
| Explore.md.claude/agents/ | 3.1 days | |
|---|---|---|
| general-purpose.md.claude/agents/ | 3.1 days | |
| Plan.md.claude/agents/ | 3.1 days | |
| keys-detail.mdrules/ | 3.1 days | |
| SUPPORT.md | 3.1 days | |
| outside.mdskills/merging/ | 2.9 days | |
| README.mdquality/collectors/ | 2.6 days | |
| THREAT-MODEL.md | 2.5 days | |
| FOLDERS.mdquality/collectors/ | 2.1 days | |
| README.mdquality/ | 2.1 days | |
| Home.mdwiki/ | 2.1 days | |
| CONFIG.mdquality/ | 2 days |
12 of 44 shown
git log -1 --format=%ct -- <doc>, and -- <area> (params.areas); the doc that trails its area most, .claude/agents/Explore.md read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal, 2026-11-04: no doc trails the files it covers by more than a week; a point-in-time value, the one doc to fix, never a mean over docs. Source: Microsoft Engineering Fundamentals Playbook: Documentation (docs not updated along with the code)
Unmapped docs and dead area paths0 docs and pathsgoal ≤ 0
Docs with no usable params.areas entry, and area paths that match no other tracked file: the lag checks skip both
each doc against params.areas, and each area path through git ls-files, quality/collectors/docs/docs.mjs over 45 docs (params.doc_set) read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal, 2026-11-04: none, since the doc lag and dated-claim checks skip an unmapped doc or a dead area path without a word; above the goal, the pages action fails a pull request. Source: Microsoft Engineering Fundamentals Playbook: Documentation (docs not updated along with the code)
Complete75
Folders with README or map row90%goal ≥ 100
Top-level folders explained by a README inside them or a row in the folder map
Gap: 10 pts under goal
| (neither)wiki/ | 0 |
|---|---|
| (folder map)actions/ | 1 |
| (folder map)config/ | 1 |
| (folder map)pages/ | 1 |
| (README and folder map)quality/ | 1 |
| (folder map)rules/ | 1 |
| (folder map)skills/ | 1 |
| (folder map)templates/ | 1 |
| (folder map)tests/ | 1 |
| (folder map)tools/ | 1 |
top-level folders (not dot or git-ignored) with a README, or a row under "Folder map" in README.md read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: every top-level folder is explained. Source: Microsoft Engineering Fundamentals Playbook: Documentation (non-existent docs)
Community health files present100%goal ≥ 100
The files GitHub lists for a healthy project, such as a code of conduct and a support guide
| Code of conduct (CODE_OF_CONDUCT.md) | 1 |
|---|---|
| Contributing guide (CONTRIBUTING.md) | 1 |
| License (LICENSE) | 1 |
| Pull request template (.github/PULL_REQUEST_TEMPLATE.md) | 1 |
| README (README.md) | 1 |
| Support file (SUPPORT.md) | 1 |
each of 6 community health files (params.community_files) at any of its paths read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: every community health file is there. Sources: GitHub Docs: About community profiles for public repositories (README, code of conduct, license, contributing); GitHub Docs: Adding support resources to your project; GitHub Docs: Creating a default community health file (pull request template). The issue template and the security policy are measured as issues.templates_present and security.policy_on
Visual share50
Text-only docs0 docsgoal ≤ 0
Docs that are nearly all prose, with hardly a table, diagram, chart, image or code block
docs under 50% visual lines, by top-level folder, quality/collectors/docs/docs.mjs over 45 docs (params.doc_set) read 2026-11-21 13:37 UTC
Goal: Git Crafter goal, 2026-11-10: no doc under 50% visual lines, since the owner asks for every doc to be as visual as possible, with as little text as possible (rules/writing-and-gates.md, Visual first); the template goal is 20%. Source: Microsoft Style Guide: Scannable content (dense text set out as lists and tables)
Speed
Each doc read in two minutes at 238 words a minute.
Reading time100
Docs over 2 minutes to read0 docsgoal ≤ 0
Docs that take longer to read than the reading goal, counted by folder
docs over 2 minutes at 238 words a minute, counted by top-level folder, quality/collectors/docs/docs.mjs over 45 docs (params.doc_set) read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: 2 minutes or less to read each doc, at 238 words a minute, the mean silent reading rate for English non-fiction. Sources: Brysbaert, 2019: How many words do we read per minute? (Journal of Memory and Language 109); Microsoft Style Guide: Top 10 tips for Microsoft style and voice (shorter is always better)
Consumption
No doc runs past its reading goal, so Claude loads no tokens past it.
Tokens100
Tokens past the reading goal0 tokensgoal ≤ 0
Tokens Claude loads from docs beyond the length a reader finishes within the reading goal
bytes / 4 of each doc, the share of its words past 476 (2 minutes at 238 words a minute), summed; detail is the heaviest docs, quality/collectors/docs/docs.mjs over 45 docs (params.doc_set) read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: no doc runs past what a reader finishes in 2 minutes at 238 words a minute, so Claude loads no tokens past it; the near band is a Git Crafter default. Sources: Brysbaert, 2019: How many words do we read per minute? (Journal of Memory and Language 109); Claude Code Docs: How Claude remembers your project (longer files consume more context); Claude Docs: Skill authoring best practices (concise is key)
Issues
Quality
72
9 of 9 measured
Speed
50
2 of 2 measured
Consumption
50
1 of 1 measured
Ideal state
Issues hold bugs and quick fixes: typed, labeled by area, closed within a day, a bug by its pull request. Features wait on the board.
| Part | Ideal | Set up |
|---|---|---|
| Issues | Only bugs and quick fixes, each typed, labeled by area, shown as a table or image, a bug closed by its pull request | Use the organization's Bug and Task issue types; file with gh issue create and its type flag |
| Intake | Two valid forms, Bug and Quick fix, and no blank issue | Each form sets its type; config.yml turns blank issues off |
| Labels | Area labels only; the type says what kind; a label nothing uses is archived | Archive through the labels API or the Labels page; history stays on old issues |
| Milestones | None open, unless a dated goal spans several issues | Give each a due date and close it when done |
| Views | Shared, pinned views, each the search behind one metric | Create them in the Issues sidebar; GitHub offers no API for views |
| Features | A draft card on the board; an issue only while its pull request is open | Convert the draft and add its area label when the pull request opens |
16 sources, newest 2026-11-10
- GitHub Docs: About issues 2026-11-10
- GitHub Docs: Quickstart for GitHub Issues 2026-11-10
- GitHub Docs: Managing issue types in an organization 2026-11-10
- GitHub Docs: Syntax for issue forms 2026-11-10
- GitHub Docs: Configuring issue templates for your repository 2026-11-10
- GitHub Docs: Managing labels 2026-11-10
- GitHub Docs: REST API endpoints for labels 2026-11-10
- GitHub Changelog: Label archiving is generally available 2026-08-27
- GitHub Docs: About milestones 2026-11-10
- GitHub Changelog: Saved views for repository issues 2026-06-25
- GitHub Docs: Linking a pull request to an issue 2026-11-10
- GitHub Docs: Adding items to your project (draft issues) 2026-11-10
- GitHub Docs: Creating diagrams 2026-11-03
- Claude Code Docs: Claude Code GitHub Actions 2026-11-10
- Claude Code Action: Solutions and use cases (issue triage) 2026-11-10
- Microsoft Learn: Manage work with GitHub Projects 2026-11-10
Quality
Valid forms, every issue typed, labeled and shown as a table, no parked work or unused labels, every bug closed by a merged pull request.
Issues71
Issues with an area label74.4%goal ≥ 100
Share of issues tagged with the part of the project they affect; higher is better.
Gap: 25.6 pts under goal
| with an area label | 32 | |
|---|---|---|
| without | 11 |
gh api graphql: repository.issues (labels) read 2026-11-21 13:37 UTC
Goal: template goal: every issue names its area, so it reaches whoever owns that area
Open bugs1 bugsgoal ≤ 0
Problems that were reported and are not fixed yet; fewer is better.
Gap: 1 bugs over goal
| quality | 0 bugs | |
|---|---|---|
| pages | 1 bugs | |
| guard | 0 bugs | |
| ci | 0 bugs | |
| documentation | 0 bugs | |
| security | 0 bugs | |
| accessibility | 0 bugs | |
| templates | 0 bugs |
gh api graphql: repository.issues (open: issueType, labels); on a user's repo, labels read 2026-11-21 13:37 UTC
Goal: template goal: no known bug left open
Parked issues2 issuesgoal ≤ 0
Open issues over a day old that are not a bug or a quick fix; such work waits on the board. Fewer is better.
Gap: 2 issues over goal
| no type | 2 issues |
|---|
state: gh api graphql: repository.issues (open: createdAt, issueType), against params.issue_types and params.park_hours read 2026-11-21 13:37 UTC
Goal: GitHub docs, Managing issue types in an organization (read 2026-11-10): a type says what kind of work an issue is; GitHub docs, Adding items to your project (read 2026-11-10): a draft issue captures an idea on the board; template goal: none parked
Unused labels0 labelsgoal ≤ 0
Labels in the picker that no issue or pull request carries and no setting names; fewer is better.
state: gh api repos/SoulCraft-Org/git-crafter/labels (archived_at) and gh api graphql: repository.labels (issues and pullRequests totalCount), against params.bug_label and params.area_labels read 2026-11-21 13:37 UTC
Goal: GitHub docs, Managing labels (read 2026-11-10), and GitHub changelog, Label archiving is generally available (2026-08-27): an archived label leaves the picker and keeps its history; template goal: none unused
Issue forms in order100%goal ≥ 100
Share of intake checks that hold: each issue form parses, each sets a type, blank issues are off. Higher is better.
| every issue form parses, with a name, a description and a body | 1 | |
|---|---|---|
| every form sets a type: Bug, Task | 1 | |
| config.yml turns blank issues off | 1 |
state: .github/ISSUE_TEMPLATE, each YAML issue form parsed (name, description, body, type) and config.yml (blank_issues_enabled); the type check is against params.issue_types read 2026-11-21 13:37 UTC
Goal: GitHub docs, Syntax for issue forms and Configuring issue templates for your repository (read 2026-11-10): a form needs a name, a description and a body, may set its issue type, and config.yml turns blank issues off; template goal: every check holds
Bugs closed by a merged PR100%goal ≥ 100
Share of recently fixed bugs that an accepted code change closed, not a close by hand; higher is better.
| closed by a merged PR | 5 | |
|---|---|---|
| closed another way | 0 |
gh api graphql: repository.issues, last 20 bugs closed as completed (issueType; on a user's repo, labels; ClosedEvent closer) read 2026-11-21 13:37 UTC
Goal: GitHub docs, Linking a pull request to an issue: a merged pull request with a closing keyword closes its issue; template goal: every fixed bug closes that way
Issues reopened0%goal ≤ 5
Share of recently closed reports that had been reopened because a fix did not hold; lower is better.
| reopened at least once | 0 |
|---|---|
| closed issues read | 20 |
gh api graphql: repository.issues, last 20 closed as completed (REOPENED_EVENT) read 2026-11-21 13:37 UTC
Goal: template goal: one fix in twenty fails to hold at most
Cards75
Prose words, the latest card0 wordsgoal ≤ 75
Words the latest issue spends outside tables, diagrams and code; fewer is better, so the visuals carry it.
| the latest issue #169, opened 2026-11-20 | 0 words |
|---|---|
| newer issues with an empty body, passed over | 0 |
gh api graphql: of the 20 newest issues (body), the latest with a body; words outside tables, fenced code and diagrams, inline code and HTML comments (proseWords in github.mjs) read 2026-11-21 13:37 UTC
Goal: template goal: a card reads in under 20 seconds; adults read non-fiction at about 238 words a minute (Brysbaert, How many words do we read per minute?, Journal of Memory and Language, 2019), so 75 words take about 19 seconds
Speed
Each issue closes within a day, and none waits more than two.
Issues50
Oldest open issue8.7 daysgoal ≤ 2
How long the longest-waiting open issue has been open, in days; lower is better.
Gap: 6.7 days over goal
| #19 | 8.7 days |
|---|
gh api graphql: repository.issues (open) read 2026-11-21 13:37 UTC
Goal: template goal: no issue waits more than two days
Latest issue's hours to close10.8 hoursgoal ≤ 24
How long the most recently fixed issue took from filed to closed, in hours; lower is better.
| #125 | 10.8 hours |
|---|
gh api graphql: repository.issues, the latest closed as completed (createdAt, closedAt) read 2026-11-21 13:37 UTC
Goal: template goal (2026-11-03): an issue closes within a day of being filed
Consumption
A fix uses no more runner time than a typical merged pull request.
Cost50
Runner minutes per issue, the latest fix72 minutesgoal ≤ 60
Billed runner minutes the CI runs of the latest pull request that closed an issue took, per issue it closed
Gap: 12 minutes over goal
| claude-review | 4 minutes | |
|---|---|---|
| cloud-test | 6 minutes | |
| pages | 27 minutes | |
| pr-body | 4 minutes | |
| secret-scan | 5 minutes | |
| verify | 26 minutes |
latest: GraphQL pullRequests closingIssuesReferences: the latest merged pull request that closed an issue; its runs (gh api actions/workflows/{id}/runs) and their REST jobs' billed runner minutes (one call per run at most, each read once), over the issues it closed; #140 closed 1 issue read 2026-11-21 13:37 UTC
Goal: template goal (2026-11-03): a fix uses no more runner time than a merged pull request, 60 billed runner minutes, near 100, as for ci.latest_pr_dollars
Pull requests
Quality
95
10 of 10 measured
Speed
50
6 of 6 measured
Consumption
100
1 of 1 measured
Ideal state
Each change is a small pull request, stacked when large, linked to its issue, reviewed at its green head, and merged within the hour.
| Part | Ideal | Set up |
|---|---|---|
| Pull requests list | A short queue: each open pull request is under a day old, green and free of conflicts | Open one small pull request per change; the Claude app's monitor with Auto-fix repairs red checks and conflicts |
| Description | A table of facts, a diagram where a flow changed, a linked issue or card, and few prose words | Fill the pull request template; write Closes or Part of before the issue number |
| Authored by me | An author's list empties the same day; no change is over 400 reviewed lines | One change and its test per pull request; split a large one, or stack it, before review |
| Review requests | No request waits past an hour of green; the review reads the head commit that merges | Request a person or team; where one account authors and merges, post a verdict comment naming the head commit |
| Assigned and Involves me | Nothing sits assigned or mentioned without an answer; every review thread is resolved before the merge | Assign whoever merges; answer or resolve each comment; a blocked pull request names what it waits on |
| Labels and Milestones | Labels come from automation, such as dependencies and area; a milestone only where a release is planned | Let Dependabot label its pull requests; leave Milestones empty unless a release needs one |
| Stacks | A large change is a stack of small pull requests based on the default branch, merged bottom up, never into a side branch | Create it with gh stack or the stacks API; the base branch's rules and checks then apply to every layer |
| Merge | Squashed at the reviewed head within the hour of green, with every check passed and the branch deleted, never reverted | Allow squash only, delete head branches, and require the CI check in a ruleset; merge pinned to the reviewed commit |
16 sources, newest 2026-11-10
- GitHub Docs: Helping others review your changes 2026-11-10
- GitHub Docs: About stacked pull requests 2026-11-10
- GitHub Docs: Linking a pull request to an issue 2026-11-04
- GitHub Docs: Merging stacked pull requests 2026-11-10
- GitHub Changelog: Stacked pull requests generally available 2026-10-06
- GitHub Changelog: Refreshed repository pull requests page generally available 2026-09-21
- GitHub Docs: Requesting a pull request review 2026-11-10
- GitHub Docs: Approving a pull request with required reviews 2026-11-10
- GitHub Docs: Available rules for rulesets 2026-11-10
- GitHub Docs: About merge methods on GitHub 2026-11-10
- GitHub Docs: Searching issues and pull requests 2026-11-10
- Microsoft Engineering Fundamentals Playbook: Pull Requests 2024-02-15
- Claude Code Docs: Best practices for Claude Code 2026-11-10
- Claude Code Docs: Desktop application, monitoring pull request status 2026-11-10
- Google Engineering Practices: Small CLs 2026-11-03
- DORA: the four keys of software delivery performance 2026-01-05
Quality
Green and reviewed at the merged head, right at first review, small or stacked, described in a table, linked to an issue, never reverted.
Holds up90
Fixed after the first review40%goal ≤ 25
Share of reviewed changes that needed another commit after their first review; lower means more pass first time.
Gap: 15 pts over goal
| fixed after the first review | 8 | |
|---|---|---|
| merged as first reviewed | 12 | |
| no review before merge (left out) | 0 |
gh api graphql: last 20 merged pullRequests (headRefOid; reviews' commit.oid, submittedAt, author type; members' Review: MERGE|BLOCK at <sha> comments) read 2026-11-21 13:37 UTC
Goal: template goal: three in four reviewed changes pass their first review
Merged PRs green at head100%goal ≥ 100
Share of accepted code changes whose automatic checks all passed at the end; higher is better.
| green | 20 | |
|---|---|---|
| red or pending | 0 | |
| no checks (left out) | 0 |
gh api graphql: last 20 merged pullRequests (head statusCheckRollup: SUCCESS, or each check's latest run passed) read 2026-11-21 13:37 UTC
Goal: GitHub docs, About protected branches: Require status checks before merging; template goal: every check passes at the merged head
Merged PRs reviewed at head100%goal ≥ 100
Share of accepted code changes that a person reviewed at the exact commit that was accepted; higher is better.
| reviewed at the merged head | 20 | |
|---|---|---|
| reviewed another commit, or after merge | 0 | |
| not reviewed | 0 |
gh api graphql: last 20 merged pullRequests (headRefOid, mergedAt; reviews' commit.oid, submittedAt, author type; members' Review: MERGE|BLOCK at <sha> comments) read 2026-11-21 13:37 UTC
Goal: GitHub docs, About protected branches: Require pull request reviews before merging, and Dismiss stale pull request approvals when new commits are pushed, so a review covers the commit that merges
Reverts in the last 20 merges0 PRsgoal ≤ 1
Recent accepted changes that undo an earlier one, because something broke; fewer is better.
gh api graphql: last 20 merged pullRequests (title, mergedAt); a revert is titled Revert "<title>" read 2026-11-21 13:37 UTC
Goal: DORA, Accelerate State of DevOps Report 2023: elite teams' change failure rate is 5% and high performers' 10%, which is 1 and 2 of the last 20 merges
Merged outside the default branch0 PRsgoal ≤ 0
Recent accepted changes merged into a side branch, where the default branch's rules may not apply; fewer is better.
gh api graphql: last 20 merged pullRequests (baseRefName, baseRepository.defaultBranchRef.name, stack) read 2026-11-21 13:37 UTC
Goal: GitHub docs, About stacked pull requests (read 2026-11-10): a stack's merge requirements come from the bottom pull request's base branch, and outside a stack rules and checks often only trigger for the bottom pull request; template goal: every change merges into the default branch, a large one as a stack
Size100
Prose words, the latest PR description32 wordsgoal ≤ 50
Words the latest accepted change's description spends outside tables, code and diagrams; fewer is better.
| #140 | 32 words |
|---|---|
| newer merges with an empty description, passed over | 0 |
gh api graphql: of the last 20 merged pullRequests (body), the latest with a description; words outside tables, fenced code and diagrams, inline code and HTML comments (proseWords in github.mjs) read 2026-11-21 13:37 UTC
Goal: Git Crafter goal (the owner, 2026-11-10): everything in a pull request is as visual as possible, with as few words as possible. 50 prose words is about three short lines beside the tables and diagrams, which this count leaves out; near is the template's 150. The latest description read 136 words (the live page, 2026-11-10)
Lines changed, the latest PR166 linesgoal ≤ 200
Lines the latest accepted change asks a reviewer to read, less lockfiles, snapshots and moved lines; lower is better.
| #140 | 166 lines |
|---|---|
| lockfile and snapshot lines left out | 0 lines |
| moved lines left out | 0 lines |
gh api graphql: the latest merged pullRequest (additions, deletions, files, mergeCommit); git diff of its merge commit for moved lines read 2026-11-21 13:37 UTC
Goal: SmartBear's code review study at Cisco: a reviewer should take in no more than 200 to 400 lines at a time (SmartBear, Best Kept Secrets of Peer Code Review, 2006)
Share over 400 lines0%goal ≤ 10
Share of accepted changes too big to review in one sitting; lower is better.
| over 400 lines | 0 | |
|---|---|---|
| 400 lines or fewer | 20 |
gh api graphql: last 20 merged pullRequests (additions, deletions, files, mergeCommit); git diff of each merge commit for moved lines read 2026-11-21 13:37 UTC
Goal: SmartBear's code review study at Cisco: a reviewer should take in no more than 200 to 400 lines at a time (SmartBear, Best Kept Secrets of Peer Code Review, 2006); the 10% share is a template goal
Speed
Reviewed and merged within the hour of going green, with a short queue, no conflicts and nothing left waiting.
Flow75
Latest PR's hours to merge10.8 hoursgoal ≤ 4
How long the most recently merged pull request took from opened to merged, in hours, by stage; lower is better.
Gap: 6.8 hours over goal
| #140, open to merge | 10.8 hours | |
|---|---|---|
| open to all green | 10.8 hours | |
| all green to review | 0 hours | |
| review to merge | 0 hours |
gh api graphql: the latest merged pullRequest (createdAt, mergedAt; head check times; reviews) read 2026-11-21 13:37 UTC
Goal: Git Crafter goal (2026-11-10): the org's open-merge goal in goals.json, 4 hours and near 24, in place of the template's DORA day and week, so this metric has one goal. Under the template's goal a 92.3 hour merge rated near (the live page, 2026-11-10)
Minutes from all green to merge0 minutesgoal ≤ 30
Minutes a merged PR waited from all checks green at its head to merge, median of the last 10; lower is better.
| #140 | 0 minutes | |
|---|---|---|
| #139 | 0 minutes | |
| #138 | 0 minutes | |
| #137 | 0 minutes | |
| #136 | 0 minutes | |
| #135 | 0 minutes | |
| #134 | 0 minutes | |
| #124 | 0 minutes | |
| #122 | 0 minutes | |
| #120 | 0 minutes |
gh api graphql: the last 10 merged pullRequests (N = 10, a template choice), median of mergedAt minus the last check's completion on the merged head, for each PR whose head rollup is SUCCESS read 2026-11-21 13:37 UTC
Goal: Git Crafter goal, no public benchmark (the orchestrator, 2026-11-05): a PR merges within 30 minutes of all checks going green, since the merge waits only on the head-pinned review; near is 2 hours. Google's review-speed guide (google.github.io/eng-practices/review/reviewer/speed.html, read 2026-11-04) sets one business day as the slowest response, which this goal sits well inside
Queue38
Open PRs now22 PRsgoal ≤ 10
Code changes waiting right now to be checked and accepted, by how long each has waited; fewer is better.
Gap: 12 PRs over goal
| under a day | 4 PRs | |
|---|---|---|
| 1 to 3 days | 18 PRs | |
| 3 to 7 days | 0 PRs | |
| a week or more | 0 PRs |
gh api graphql: open pullRequests (createdAt) read 2026-11-21 13:37 UTC
Goal: template goal: a queue short enough to review in one sitting
Longest wait after all green1,962 minutesgoal ≤ 30
Minutes the longest-waiting open change has sat since its checks passed, unreviewed or unmerged; lower is better.
Gap: 1,932 minutes over goal
| #150, awaiting review | 1,962 minutes | |
|---|---|---|
| #151, awaiting review | 1,960 minutes | |
| #152, awaiting review | 1,960 minutes | |
| #153, awaiting review | 1,960 minutes | |
| #154, awaiting review | 1,960 minutes | |
| with a pending review request | 0 PRs |
gh api graphql: open pullRequests (isDraft, author; head statusCheckRollup and check times; reviews, reviewDecision, reviewRequests; members' Review: MERGE|BLOCK at <sha> comments) read 2026-11-21 13:37 UTC
Goal: Git Crafter goal, no public benchmark (2026-11-10): the same 30 minutes, near 2 hours, as pull_requests.green_to_merge_minutes, which it reads on open pull requests instead of merged ones
Oldest open PR2.2 daysgoal ≤ 1
How long the longest-waiting code change has sat open and undecided, in days; lower is better.
Gap: 1.2 days over goal
| #147 | 2.2 days |
|---|---|
| #148 | 2.2 days |
| #150 | 1.4 days |
| #151 | 1.4 days |
| #152 | 1.4 days |
gh api graphql: open pullRequests (createdAt) read 2026-11-21 13:37 UTC
Goal: Git Crafter goal (2026-11-10): the latest merge takes at most 4 hours, near 24 (goals.json open-merge), so no pull request stays open past a day; near is 3 days. Under the template's week a pull request open 3.8 days still met the goal
Open PRs with a conflict0 PRsgoal ≤ 0
Waiting changes that clash with the latest default branch and must be fixed before they can merge; fewer is better.
gh api graphql: open pullRequests (mergeable), read again after 5 s while GitHub is still computing it read 2026-11-21 13:37 UTC
Goal: template goal: no waiting change needs a rebase
Consumption
Each merged change uses little runner time: few pushes, cheap checks.
Cost100
Runner dollars at list price, the latest merged PR0.23 dollarsgoal ≤ 0.36
Runner dollars the CI runs of the latest merged pull request cost; small, right-first-time changes cost less
| claude-review | 0.01 dollars | |
|---|---|---|
| cloud-test | 0.01 dollars | |
| pages | 0.12 dollars | |
| pr-body | 0.01 dollars | |
| secret-scan | 0.01 dollars | |
| verify | 0.07 dollars |
latest: gh api pulls (the latest of the last 20 merged) and actions/workflows/{id}/runs (its branch runs and merge commit runs); their REST jobs, one call per run at most, each read once and most already read for the queue sample: each job's billed minutes times its runs-on label's rate from GitHub docs, Actions runner pricing; #140 read 2026-11-21 13:37 UTC
Goal: template goal: 60 runner minutes a merged pull request, near 100, priced at GitHub's standard Linux 2-core rate of $0.006 a minute (GitHub docs, Actions runner pricing, read 2026-11-03): 60 x $0.006 = $0.36, 100 x $0.006 = $0.60
Discussions
Quality
–
0 of 0 measured
Speed
–
0 of 0 measured
Consumption
–
0 of 0 measured
Ideal state
Questions and ideas live in Discussions, sorted by category; each question gets a quick first reply and a marked answer, and work moves to issues.
2 sources, newest 2026-11-13
- GitHub Docs: About discussions 2026-11-13
- GitHub Docs: Managing categories for discussions 2026-11-13
Quality
Every answered question has a marked answer, and every category is in use.
No quality metric yet.
Speed
A new discussion gets its first reply within a day.
No speed metric yet.
Consumption
Discussions cost no runner minutes.
No consumption metric yet.
Actions
Quality
100
9 of 9 measured
Speed
100
4 of 4 measured
Consumption
100
6 of 6 measured
Ideal state
Every push gets a trusted result within ten minutes from locked workflows, and included minutes last the cycle, free lanes first, no unneeded runs.
| Part | Ideal | Set up |
|---|---|---|
| Workflows | Each workflow starts only when a file it checks changed, holds a read-only token, and a newer push cancels its older run | Add paths filters or a changes job, permissions contents: read at the top, concurrency with cancel-in-progress, and a timeout on each job |
| Caches | Every install restores a cache keyed on its lockfile, and storage stays under the repo's 10 GB so nothing is evicted early | setup-node with cache: npm, or actions/cache keyed on hashFiles of the lockfile; entries unused for 7 days are removed |
| Lockfile | Every workflow runs the action commits its lockfile records, and a workflow outside the lockfile cannot run | Run gh actions-lock, commit .github/workflows/actions.lock, check it in CI, then turn on the Require lockfile policy |
| Runners | Light jobs run on ubuntu-slim at a third of the 2-core price, and free third-party minutes are used before included ones | ubuntu-slim for one-core jobs under 15 minutes; Blacksmith gives 3,000 and Ubicloud 1,250 free minutes a month; public repos run free |
| Deployments | Only the default branch deploys, through an environment, with OIDC in place of a stored secret | Create the environment and limit its deployment branches to the default branch; required reviewers on a private repo need Enterprise |
| Usage metrics | Included usage lasts the whole billing cycle, and the workflows and jobs that bill the most are trimmed first | Insights, Actions Usage Metrics by workflow, job and runner; a budget stops Actions at the included amount, which resets each cycle |
| Performance metrics | Jobs start within 30 seconds, few fail, and the pipeline goes green within ten minutes | Insights, Actions Performance Metrics: run time, queue time and failures by workflow and job; this tab scores job wait and failed runs |
| Attestations | Every release, binary or package people download carries signed build provenance; test builds carry none | actions/attest with id-token: write, attestations: write and contents: read; consumers run gh attestation verify |
20 sources, newest 2026-11-11
- GitHub docs: Secure use reference, lockfiles, pinning and least privilege 2026-11-10
- GitHub docs: Workflow dependency lockfiles 2026-11-10
- GitHub docs: Locking action dependencies in a repository's workflows 2026-11-10
- GitHub docs: Governing execution of GitHub Actions workflows 2026-11-10
- GitHub docs: Dependency caching reference, limits and eviction 2026-11-10
- GitHub docs: About GitHub Actions metrics, usage and performance 2026-11-10
- GitHub docs: Artifact attestations 2026-11-10
- GitHub docs: GitHub Actions billing, included usage and runner rates 2026-11-10
- GitHub docs: Actions runner pricing 2026-11-10
- GitHub docs: GitHub-hosted runners reference, ubuntu-slim 2026-11-10
- GitHub docs: Deployments and environments 2026-11-10
- GitHub docs: Using artifact attestations 2026-11-10
- Microsoft Learn: Security considerations for DevOps platforms 2026-01-15
- Claude Code docs: Claude Code GitHub Actions, permissions and cost 2026-11-10
- GitHub docs: Workflow syntax, paths filters, concurrency and permissions 2026-11-10
- DORA: Capabilities, continuous integration 2026-11-10
- GitHub changelog: Actions workflow lockfiles are generally available 2026-10-28
- Martin Fowler: Continuous Integration 2024-01-18
- Blacksmith: Pricing, 3,000 free minutes a month 2026-11-11
- Ubicloud: GitHub Actions runners, 1,250 free minutes a month 2026-11-11
Pipeline: the latest push to all green
The slowest step of each stage95% or more pass85 to 94%Under 85%Not measuredRuns on the laptopA personBlue bar: median minutes
Pull request checks1.1 min
-
cloud-test
- Median
- 1.1 minutes
- Pass rate
- 100% of runs passed; cancelled runs are left out
- What runs
- On every pull request touching .github/workflows/cloud-test.yml, .github/cloud-test.json: cloud-test on ubuntu-slim: uses actions/checkout, uses actions/setup-node, Install Git Crafter's packages, Run the allowlisted script
- Defined in
- .github/workflows/cloud-test.yml
- Kind
- An automated workflow: a GitHub Actions workflow or a Cloudflare build
- Path
- The slowest step in its stage, on the rail
-
claude-review
- Median
- 0.1 minutes when it does its work
- Skips
- 25% of sampled runs found nothing to check
- Pass rate
- 100% of runs passed; cancelled runs are left out
- What runs
- On every pull request touching .github/workflows/**, actions/**, tools/claude_deny*, tools/hookify_check.py, rules/**, skills/**, .claude/**: gate on ubuntu-slim, then review on ubuntu-latest, if there is work
- Defined in
- .github/workflows/claude-review.yml
- Kind
- An automated workflow: a GitHub Actions workflow or a Cloudflare build
-
pages
- Median
- Not timed
- Pass rate
- not measured
- What runs
- On every pull request touching pages/**, goals.json, process.json, maps.json, data/**, tools/**, knip.json, quality/**, config/quality.json, config/quality/**, package.json, package-lock.json, actions/**, tests/action-config.json, .github/workflows/pages.yml, **/*.md: runner on ubuntu-slim and changes on ubuntu-slim, …
- Defined in
- .github/workflows/pages.yml
- Kind
- An automated workflow: a GitHub Actions workflow or a Cloudflare build
-
pr-body
- Median
- Not timed
- Pass rate
- not measured
- What runs
- On every pull request: pr-body on ubuntu-slim: uses actions/checkout, The description links its issue or card, and the change is within the lines goal
- Defined in
- .github/workflows/pr-body.yml
- Kind
- An automated workflow: a GitHub Actions workflow or a Cloudflare build
-
secret-scan
- Median
- Not timed
- Pass rate
- not measured
- What runs
- On every pull request: secret-scan on ubuntu-slim: uses actions/checkout, Install gitleaks (pinned release, SHA-256 checked), Self-test (the scan's range, with a planted fake key), Scan the commits this run answers for
- Defined in
- .github/workflows/secret-scan.yml
- Kind
- An automated workflow: a GitHub Actions workflow or a Cloudflare build
-
verify
- Median
- Not timed
- Pass rate
- not measured
- What runs
- On every pull request: runner calls ./.github/workflows/ci-overflow.yml and dependency-review on ubuntu-slim, then ci calls ./.github/workflows/ci-standard.yml
- Defined in
- .github/workflows/verify.yml
- Kind
- An automated workflow: a GitHub Actions workflow or a Cloudflare build
-
Review1.4 min
-
Review and merge
- Median
- 1.4 minutes
- Pass rate
- 45% of runs passed; cancelled runs are left out
- What runs
- A person reviews the pull request, then merges it; timed from all checks green to the merge
- Defined in
- branch rules on the default branch
- Kind
- A step a person takes
- Path
- The slowest step in its stage, on the rail
-
Merge to main0.2 min
-
wiki
- Median
- 0.2 minutes
- Pass rate
- 100% of runs passed; cancelled runs are left out
- What runs
- On every push to main touching wiki/**, .github/workflows/wiki.yml: wiki on ubuntu-slim: uses actions/checkout, Mirror wiki/ into the wiki
- Defined in
- .github/workflows/wiki.yml
- Kind
- An automated workflow: a GitHub Actions workflow or a Cloudflare build
- Path
- The slowest step in its stage, on the rail
-
pages
- Median
- Not timed
- Pass rate
- not measured
- What runs
- On every push to main: runner on ubuntu-slim and docs-gate on ubuntu-slim, if there is work and code-gate on ubuntu-slim, if there is work, then action on a runner chosen at run time, if there is work and action-collect on a runner chosen at run time, if there is work, then action-render on a runner chosen at run time…
- Defined in
- .github/workflows/pages.yml
- Kind
- An automated workflow: a GitHub Actions workflow or a Cloudflare build
-
secret-scan
- Median
- Not timed
- Pass rate
- not measured
- What runs
- On every push to main: secret-scan on ubuntu-slim: uses actions/checkout, Install gitleaks (pinned release, SHA-256 checked), Self-test (the scan's range, with a planted fake key), Scan the commits this run answers for
- Defined in
- .github/workflows/secret-scan.yml
- Kind
- An automated workflow: a GitHub Actions workflow or a Cloudflare build
-
verify
- Median
- Not timed
- Pass rate
- not measured
- What runs
- On every push to main: runner calls ./.github/workflows/ci-overflow.yml, then ci calls ./.github/workflows/ci-standard.yml
- Defined in
- .github/workflows/verify.yml
- Kind
- An automated workflow: a GitHub Actions workflow or a Cloudflare build
-
Every step as a table
| Stage | Step | Kind | Median | Pass rate |
|---|---|---|---|---|
| Pull request checks | cloud-test (rail) | Workflow | 1.1 min | 100% |
| Pull request checks | claude-review | Workflow | 0.1 min | 100% |
| Pull request checks | pages | Workflow | not timed | not measured |
| Pull request checks | pr-body | Workflow | not timed | not measured |
| Pull request checks | secret-scan | Workflow | not timed | not measured |
| Pull request checks | verify | Workflow | not timed | not measured |
| Review | Review and merge (rail) | Person | 1.4 min | 45% |
| Merge to main | wiki (rail) | Workflow | 0.2 min | 100% |
| Merge to main | pages | Workflow | not timed | not measured |
| Merge to main | secret-scan | Workflow | not timed | not measured |
| Merge to main | verify | Workflow | not timed | not measured |
Quality
No flaky reruns, installs restore their cache, and every workflow runs the commits its lockfile records.
Reliable100
Actions hardening100
GITHUB_TOKEN reads only by default1 on/offgoal ≥ 1
Whether a workflow's token can only read unless the workflow asks for more; on is better.
| GITHUB_TOKEN reads only, by default | 1 |
|---|---|
| Actions may approve pull requests | 0 |
gh api repos/SoulCraft-Org/git-crafter/actions/permissions/workflow (default_workflow_permissions, can_approve_pull_request_reviews) read 2026-11-21 13:37 UTC
Goal: GitHub docs, Security hardening for GitHub Actions: grant the GITHUB_TOKEN the least access it needs; Managing GitHub Actions settings for a repository: Workflow permissions
Privileged jobs running pull request code0 jobsgoal ≤ 0
Jobs that run with the repo's secrets on a pull request's own code; none is the only safe number.
.github/workflows/*.yml: jobs of a pull_request_target or workflow_run workflow that check out the pull request's code: an actions/checkout of its head ref or repo, gh pr checkout, or a git fetch or checkout of refs/pull/* read 2026-11-21 13:37 UTC
Goal: GitHub docs, Security hardening for GitHub Actions: pull_request_target and workflow_run, used with a checkout of an untrusted pull request, expose the repo; OpenSSF Scorecard, Dangerous-Workflow
Trust100
Test job pass rate on main100%goal ≥ 95
Share of the latest runs on main whose test job passed; cancelled runs and runs with no site change are left out
| Passed | 12 runs |
|---|---|
| Failed | 0 runs |
| Cancelled, left out | 0 runs |
| No site change, test job skipped, left out | 0 runs |
last N runs: gh api runs of each workflow in params.workflows (newest 100 runs a workflow), with GraphQL check runs: the last 20 runs on main of each workflow that runs there; a run counts when a test job ran, and cancelled runs and runs that skipped every test job are left out. N is 20 (ci.mjs's LAST_RUNS): enough to turn over within hours where the test workflows run many times a day read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: the test jobs pass on main nearly every time, so a red run means a real break
Skipped and todo tests0 testsgoal ≤ 0
Tests marked skip, todo or fixme, which never run; skips on a condition are read from code and shown apart
| Not counted, on a condition: skipIf, runIf or a skip at run time | 9 |
|---|
state: git ls-files in params.suites; skip, todo and fixme markers in code lines, a marked block by its cases. skipIf, runIf and run-time skips are read from code, not CI, and shown apart read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: no test skips unconditionally; a skipped test checks nothing
Speed
Push to all green within ten minutes; a red default branch fixed within ten minutes.
Fast100
Pipeline: the latest push to all green1.8 minutesgoal ≤ 4
Minutes from the latest pull request push to every check passing; the drawing shows each step's latest run
.claude/settings.json, the git hooks in params.hooks_dir, .github/workflows, params.stages; gh api actions/workflows/{id}/runs (the latest pull request head that went all green; each stage's latest run, pass rates from the last 20 runs per workflow), pulls and check-runs (the latest of the last 20 merges) read 2026-11-21 13:37 UTC
Goal: Git Crafter goal (2026-11-10): the 90th percentile of 15 readings 2026-11-04 to 2026-11-11 (data/quality/history and the 12 quality-run artifacts GitHub still keeps), which read 1.7 to 4.3 minutes, so a slowdown shows; near is the template's ten-minute build. Under the template's 10 it met its goal in every reading
Job wait for a runner5.5 secondsgoal ≤ 30
Seconds a job waits between being queued and starting on a runner, at the 90th percentile; lower is better
| branch-cleanup | 3 seconds | |
|---|---|---|
| cloud-test | 5.2 seconds | |
| pages | 5.7 seconds | |
| scorecard | 3.9 seconds | |
| wiki | 3 seconds |
last 10 completed runs per workflow, the queue sample the CI tab already reads (gh api actions/runs/{id}/jobs): each job's started_at less created_at read 2026-11-21 13:37 UTC
Goal: GitHub docs, Actions metrics (read 2026-11-10): the performance view reports average queue time and sets no number; template goal: nine jobs in ten start within 30 seconds, near 60
Reliable100
Minutes the default branch is red0 minutesgoal ≤ 10
How long a workflow on the default branch has been failing, right now; 0 when every one passed last; lower is better
| workflows green on main | 4 |
|---|
gh api actions/workflows/{id}/runs: each active workflow whose file still runs on a push to the default branch, its runs there, newest first; red from the end of the first failure after its latest success read 2026-11-21 13:37 UTC
Goal: DORA's continuous integration capability (read 2026-11-03): a build that cannot be fixed in a few minutes has its change reverted; Martin Fowler, Continuous Integration (2024-01-18): fix broken builds immediately; template goal: 10 minutes, one build's length
Suite time100
Test job, median1.2 minutesgoal ≤ 10
Typical minutes for the job that runs the test suites, in its latest passes
| Pull requests | 1.3 minutes | |
|---|---|---|
| Pushes to main | 1.1 minutes |
last N passing jobs: gh api runs of the suite workflow in params.workflows (newest 100 runs a workflow), with GraphQL check runs: the last 20 passing test jobs. N is 20 (ci.mjs's LAST_RUNS): enough to turn over within hours where the test workflows run many times a day read 2026-11-21 13:37 UTC
Goal: goal: the ten-minute build, the same source as ci.latest_full_run_minutes (Kent Beck, Extreme Programming Explained, 2nd edition, 2004; Martin Fowler, Continuous Integration, martinfowler.com)
Consumption
Included minutes last the cycle: free lanes first, light jobs on the cheapest runner, no idle runner, and a newer push cancels the older run.
Cost100
Runner minutes, the latest push to the default branch10 minutesgoal ≤ 10
Billed runner minutes the CI runs of the latest commit pushed to the default branch took, summed over its workflows
| pages | 4 minutes | |
|---|---|---|
| secret-scan | 1 minutes | |
| verify | 5 minutes |
latest: gh api actions/workflows/{id}/runs, the push runs of the latest commit on the default branch whose runs all ended; their REST jobs' billed runner minutes (gh api actions/runs/{id}/jobs, one call per run at most, each read once), summed; 166d3a3 priced read 2026-11-21 13:37 UTC
Goal: GitHub docs, GitHub Actions billing (read 2026-11-10): each job bills its minutes rounded up, so every workflow a push starts bills at least one; template goal (2026-11-10): the runs one push starts bill at most the ten-minute build (Martin Fowler, Continuous Integration, 2024-01-18), near 20
Runner list price per billed minute0.27 centsgoal ≤ 0.4
Cents a billed runner minute costs at list price; lighter jobs on the 1-core ubuntu-slim runner bring it down
| branch-cleanup | 0.2 cents | |
|---|---|---|
| cloud-test | 0.2 cents | |
| pages | 0.44 cents | |
| scorecard | 0.6 cents | |
| wiki | 0.2 cents |
last 10 completed runs per workflow, the queue sample (gh api actions/runs/{id}/jobs): each job's billed minutes times its runs-on label's list rate, over the minutes read 2026-11-21 13:37 UTC
Goal: template goal (2026-11-10): half the billed minutes on ubuntu-slim, priced from GitHub docs, Actions runner pricing (read 2026-11-10): ubuntu-slim 0.2 cents and Linux 2-core 0.6 cents a minute, (0.2 + 0.6) / 2 = 0.4; near 0.6, every minute on the 2-core rate
GitHub API left this hour99.1%goal ≥ 50
Share of the hourly GitHub API quota still unused, REST or GraphQL, whichever is lower; every session shares it
| REST requests left of 5000 | 99.1% | |
|---|---|---|
| GraphQL points left of 5000 | 99.8% |
latest: gh api rate_limit (counts against no limit), the share of each hourly bucket still unused, the lower of REST and GraphQL; read with the CI run's token (the workflow token unless the repo passes another) read 2026-11-21 13:37 UTC
Goal: goal set from readings (2026-11-11): the account's login had 52.8% of its REST requests left right after an org collect (2,638 of 5,000, 2026-11-10 18:23 UTC) and 95.7% at a quiet hour (GraphQL 4,783 of 5,000, 2026-11-11 16:23 UTC); a goal of half left keeps a full collect's room, near a fifth
GitHub requests per pull request run28 requestsgoal ≤ 100
Requests the workflow token spent live in the newest green pull request run that collected; a replayed read costs none
| action-collect | 20 requests | |
|---|---|---|
| build | 8 requests |
latest: gh api actions/workflows/pages.yml/runs, the newest green pull_request run from SoulCraft-Org/git-crafter whose jobs printed a notice, of the newest 3; its jobs' check-run annotations, each job's GitHub requests notice (quality/gh-replay.mjs report), live REST plus GraphQL, summed; run 44485263954 read 2026-11-21 13:37 UTC
Goal: goal from issue #38 (2026-11-12); near is the 765 a pull request run spent before replay (run 43307560596's quota lines). The workflow token reports limit 5000 an hour (gh api rate_limit in runs 43307560596 and 43355450949)
Billed test job minutes, latest run2 minutesgoal ≤ 10
Runner minutes GitHub billed for the site test job and each browser test shard in their latest run
| ci / short, run 43744847284 | 2 minutes |
|---|
latest: the latest completed run of each workflow in params.workflows whose test jobs ran, on main where the workflow runs there, else its latest pull request run (newest 100 runs a workflow); GitHub bills each job by the whole minute read 2026-11-21 13:37 UTC
Goal: Git Crafter goal: its one test job, verify.yml's ci / short, at its speed goal of 10 minutes; near the same at its near band, 20. Git Crafter runs no e2e job, so the template's second 10 minutes does not apply
Projects
Quality
70
5 of 6 measured
Speed
75
2 of 2 measured
Consumption
–
0 of 1 measured
Ideal state
Features are visual cards; bugs stay in issues. A card in progress has an open pull request, and Done cards link a merged one.
| Part | Ideal | Set up |
|---|---|---|
| Cards | A feature is a draft card: a picture of its metric and steps, a table, at most 75 words | Add it on the board; convert it to an issue, with its area label, when its pull request opens |
| Pictures | One image per card: its pillar, a meter from now to goal, its steps left to right | Run the card picture tool, push the file to the cards branch, link it by its raw address |
| Fields | Status, Pillar and Area; each fact lives in one field | Create them with the Projects API; show Linked pull requests on every card |
| Views | Board, Backlog, Shipped and Stuck: each is the search behind one metric | Create views with the REST views endpoint; set no column limit |
| Workflows | Added sets Todo, a linked pull request In Progress, closed or merged Done, reopened Todo | Turn each on in the Workflows page; GitHub offers no API to edit them |
| Insights | Charts of cards by status and pillar, by area and status, and the burn up | Create them in the Insights page; never archive a card, since archived cards leave the charts |
| Sessions | One fresh session per card, ended at the merge; the card names its goal, its files and a check | Start a session per card in its own worktree; merge a green pull request before opening another |
| Limit | No count limit on cards; a card in progress has an open pull request, and open pull requests carry the limit | Move a waiting card back to Todo and name what it waits on |
18 sources, newest 2026-11-10
- GitHub Docs: Best practices for Projects 2026-11-10
- GitHub Docs: Using the built-in automations 2026-11-10
- GitHub Docs: Customizing the board layout 2026-11-10
- GitHub Docs: About insights for Projects 2026-11-10
- GitHub Docs: Using the API to manage Projects 2026-11-10
- GitHub Docs: REST API endpoints for Project views 2026-11-10
- GitHub Docs: Adding items to your project 2026-11-10
- GitHub Docs: Basic writing and formatting syntax 2026-11-10
- Claude Code Docs: Best practices for Claude Code 2026-11-10
- Claude Code Docs: Claude Code GitHub Actions 2026-11-10
- Anthropic: Effective harnesses for long-running agents 2026-11-10
- Microsoft Learn: Set Work in Progress limits in Azure Boards 2026-03-24
- Microsoft Learn: Cumulative flow, lead time and cycle time guidance 2026-11-10
- Microsoft Learn: Show bugs on backlogs and boards 2026-11-10
- DORA: Working in small batches 2025-12-08
- DORA: Work in process limits 2026-11-10
- Claude Code Docs: Manage costs effectively 2026-11-10
- Anthropic: How we built our multi-agent research system 2026-11-10
Quality
Every open card shows a picture in few words, no bug sits on the board, and each card in progress has an open pull request.
Board70
Cards read at a glance52.4%goal ≥ 100
Share of open cards with a picture and at most 75 words of prose, so the picture carries the card; higher is better.
Gap: 47.6 pts under goal
| with a picture | 11 | |
|---|---|---|
| within 75 words | 21 | |
| open cards | 21 |
gh api graphql: repositoryOwner.projectsV2 "Git Crafter" open draft and issue cards (body): a picture (hasPicture) and at most params.card_words words of prose (proseWords) read 2026-11-21 13:37 UTC
Goal: template goal: every card shows its work as a picture with few words; GitHub docs, Basic writing and formatting syntax (read 2026-11-10): an image in a body is drawn in place; Anthropic, Best practices for Claude Code (read 2026-11-10): paste the screenshot of the design, and a screenshot next to the mockup is a check; 75 words read in about 19 seconds (Brysbaert, 2019)
In progress, no open PR1 cardsgoal ≤ 0
Cards in the in-progress column that no open pull request is building: stalled or waiting; lower is better.
Gap: 1 cards over goal
| Later | 0 cards | |
|---|---|---|
| Waiting on data | 0 cards | |
| Todo | 19 cards | |
| In Progress | 1 cards | |
| Done | 10 cards | |
| No status | 1 cards | |
| In Progress, no open pull request | 1 cards |
gh api graphql: repositoryOwner.projectsV2 "Git Crafter" items (Status, linked pull requests and their state) read 2026-11-21 13:37 UTC
Goal: DORA, Work in process limits (read 2026-11-10): the point of a limit is to expose problems in the system so they can be addressed; template goal: one session builds one card, so a count of cards limits nothing, a card in progress has an open pull request, and pull_requests.open_now carries the limit on work in flight
Done cards with a merged PR100%goal ≥ 100
Share of finished board tasks that link to an accepted code change; higher is better.
| with a merged PR | 4 | |
|---|---|---|
| without | 0 | |
| made by the Quality sync, left out | 6 |
gh api graphql: repositoryOwner.projectsV2 "Git Crafter" done items (linked pull requests), less those whose body starts with the sync marker <!-- quality-metric: id --> read 2026-11-21 13:37 UTC
Goal: template goal: every finished card links the change that finished it
Bugs and fixes on board0 cardsgoal ≤ 0
Open issue cards that are a bug or a quick fix; those are issues, not cards, so lower is better.
gh api graphql: repositoryOwner.projectsV2 "Git Crafter" open issue cards (labels, issueType), against params.bug_label and params.issue_types read 2026-11-21 13:37 UTC
Goal: template goal: a bug or a quick fix is an issue and a feature is a card; GitHub docs, Managing issue types in an organization (read 2026-11-10): a type says what kind of work an issue is; Microsoft Learn, Show bugs on backlogs and boards (read 2026-11-10) lists keeping bugs off the board as one of three options
Closed issues off Done0 cardsgoal ≤ 0
Closed issues whose board card is not in the last column; a merged PR should have moved it, so lower is better.
gh api graphql: repositoryOwner.projectsV2 "Git Crafter" issue cards (issue state, Status) read 2026-11-21 13:37 UTC
Goal: template goal: a closed issue's card is Done; GitHub docs, Using the built-in automations (read 2026-11-11): the Item closed workflow sets Status when an issue closes; Git Crafter issue 791: a card stayed In Progress after its issue closed by a merged PR
Board workflows on–goal ≥ 100
Share of the built-in board workflows that are on: add, link, close and merge move a card unaided; higher is better.
gh api failed: You do not have permission to access workflows
gh api graphql: repositoryOwner.projectsV2 "Git Crafter" workflows (enabled), against params.project_workflows
Goal: GitHub docs, Using the built-in automations (read 2026-11-10): a board sets Status when an item is added, closed or merged and adds matching items; template goal: all five on, the fifth moving a card to in progress when a pull request links its issue
Speed
A card is done within three days of its first pull request, and none stays in progress past a week.
Board75
Oldest card in progress7.9 daysgoal ≤ 7
Days the longest-waiting card has sat in the in-progress column; lower is better.
Gap: 0.9 days over goal
| in progress since 2026-11-13 | 7.9 days |
|---|
gh api graphql: repositoryOwner.projectsV2 "Git Crafter" items in the in-progress column (Status updatedAt) read 2026-11-21 13:37 UTC
Goal: DORA, Working in small batches (updated 2025-12-08, read 2026-11-10): any batch of code that takes longer than a week to complete and check is too big; template goal: no card stays in progress past a week, near is two weeks
Latest card's hours to done0.5 hoursgoal ≤ 72
How long the card most recently marked done took from its first pull request opening, in hours; lower is better.
| done 2026-11-13 | 0.5 hours |
|---|
gh api graphql: repositoryOwner.projectsV2 "Git Crafter" the latest done item with a linked PR (Status updatedAt, linked PR createdAt) read 2026-11-21 13:37 UTC
Goal: template goal (2026-11-03): a task finishes within three days of its first pull request
Consumption
A card's pull requests use no more runner time than a typical merged pull request.
Cost–
Runner minutes per pull request, the latest card–goal ≤ 60
Billed runner minutes the CI runs took, per merged pull request of the card most recently marked done
#96, the latest merged pull request on the latest card, opened 2026-11-13 14:47 UTC, before 2026-11-13 16:26 UTC, where the runs read stop covering every workflow
latest: the board named by github.json's params.project_title (gh api graphql, projectsV2): of the five cards most recently moved to the done column that link merged pull requests, the newest whose runs can be priced; their runs (gh api actions/workflows/{id}/runs) and REST jobs' billed runner minutes (one call per run at most, each read once), summed and divided by those pull requests
Goal: template goal (2026-11-04): a card's pull requests use no more runner time than a merged pull request, 60 billed runner minutes, near 100, as for ci.latest_pr_dollars
Security and quality
Quality
100
2 of 2 measured
Speed
50
1 of 1 measured
Consumption
100
1 of 1 measured
Ideal state
Reporters have a private path, the threat model keeps up with its code, no alert outlives a week, and no paid security feature bills unasked.
| Part | Ideal | Set up |
|---|---|---|
| Security policy | SECURITY.md names a private reporting channel that works for this repo's visibility | Add SECURITY.md; turn on private vulnerability reporting, which GitHub offers on public repos |
| Actions | A read-only token by default; only listed actions run, each at a full commit SHA or in a lockfile | Actions settings: selected actions, required SHA pins, read-only workflow permissions |
| Claude Code | Claude Code cannot read a credential file in the repo or the home folder | Deny Read rules for .env, key and secrets paths in .claude/settings.json |
| Threat model | Each covered element has its threat, control and gap, re-read as part of routine development | THREAT-MODEL.md beside the code; name the paths it covers and the days it may trail them |
29 sources, newest 2026-11-10
- GitHub: Advanced Security plans and prices 2026-11-10
- GitHub Docs: GitHub security features 2026-11-10
- GitHub Docs: Quickstart for securing your repository 2026-11-10
- GitHub Docs: Adding a security policy to your repository 2026-11-10
- GitHub Docs: Configuring private vulnerability reporting for a repository 2026-11-10
- GitHub Docs: About Dependabot alerts 2026-11-10
- GitHub Docs: Dependabot malware alerts 2026-11-10
- GitHub Docs: Dependabot auto-triage rules 2026-11-10
- GitHub Docs: About code scanning 2026-11-10
- GitHub Docs: About secret scanning 2026-11-10
- GitHub Docs: About push protection 2026-11-10
- GitHub Docs: GitHub Code Quality 2026-11-10
- GitHub Docs: GitHub Code Quality billing 2026-11-10
- GitHub Docs: GitHub Advanced Security license billing 2026-11-10
- GitHub Docs: Secure use reference (formerly Security hardening for GitHub Actions) 2026-11-10
- GitHub Docs: Managing GitHub Actions settings for a repository 2026-11-10
- GitHub Docs: REST API endpoints for GitHub Actions permissions 2026-11-10
- GitHub Docs: Enforcing policies for GitHub Actions in your enterprise 2026-11-10
- GitHub Docs: About Dependabot on GitHub Actions runners 2026-11-10
- GitHub Docs: Dependabot options reference 2026-11-10
- GitHub Docs: Security overview dashboard metrics 2026-11-10
- OpenSSF: S2C2F framework requirements (AUD-2, ENF-1, ING-1) 2026-11-10
- Anthropic: Claude Code settings 2026-11-10
- Anthropic: Claude Code security 2026-11-10
- Anthropic: Claude Code GitHub Actions 2026-11-10
- CISA: BOD 26-04, Prioritizing Security Updates Based on Risk 2026-06-10
- Microsoft: Security Development Lifecycle (SDL) practices 2026-11-10
- Microsoft: Security Development Lifecycle, threat modeling 2026-11-10
- OpenSSF Scorecard: checks 2026-11-10
Quality
A security policy with private reporting, a current threat model, and no secret a workflow or Claude can read.
GitHub features100
Security policy1 on/offgoal ≥ 1
Whether the repo tells people how to report a vulnerability, in its own SECURITY.md or the organization's; on is better.
gh api graphql: repository.isSecurityPolicyEnabled (a SECURITY.md in the repo, or the organization's) read 2026-11-21 13:37 UTC
Goal: GitHub docs, Adding a security policy to your repository
Design review100
Threat model current with its code1 on/offgoal ≥ 1
Whether the threat model was updated since its code last changed, within the repo's days of grace; on is better.
| THREAT-MODEL.md, tools/THREAT-MODEL.md 2026-11-15; the covered code 2026-11-15 | 0 days behind |
|---|
git log at the root: the latest commit to any params.threat_model file against the latest to params.threat_model_covers read 2026-11-21 13:37 UTC
Goal: Microsoft SDL practices and its threat modeling page (read 2026-11-10): threat modeling is part of the routine development lifecycle; Git Crafter (Claude, 2026-11-10): the model may trail its code by 7 days, the tab's fix-within-a-week goal. About 25 pull requests changed a covered path on 2026-11-10, and making each edit one 476-word file had them colliding on it
Speed
No alert of any kind stays open more than a week.
Fix time50
Oldest open alert8.5 daysgoal ≤ 7
How long the longest-waiting open alert or finding has been open, in days; lower is better.
Gap: 1.5 days over goal
| oldest: code quality | 8.5 days |
|---|---|
| open alerts read | 43 |
gh api dependabot/alerts, and code-scanning/alerts and secret-scanning/alerts while those features are on, and code-quality/findings unless it answers that code quality is off: the oldest open one's age at read time read 2026-11-21 13:37 UTC
Goal: template goal: no alert waits more than a week, near 15 days; CISA's BOD 26-04 (June 10, 2026) ranks fixes by risk for federal agencies; its deadlines are in a table this read could not parse (2026-11-10), so the week is the template's own
Consumption
No paid security feature bills unless the organization bought it.
Cost100
Security features billed a month0 dollarsgoal ≤ 0
Dollars a month the organization is billed now for GitHub's paid security features; free is the goal.
| Code Security: 0 active committers | 0 dollars | |
|---|---|---|
| Secret Protection: 0 active committers | 0 dollars |
gh api orgs/{owner}/settings/billing/advanced-security (active committers billed, per product) times the list price: Code Security $30, Secret Protection $19 per active committer a month (github.com/security/plans, read 2026-11-03) read 2026-11-21 13:37 UTC
Goal: template goal: every security feature at no cost, as GitHub offers code scanning and secret scanning free on a public repo (github.com/security/plans, read 2026-11-03); near is one committer's Secret Protection
Dependabot
Quality
79
12 of 12 measured
Speed
92
6 of 6 measured
Consumption
–
0 of 1 measured
Ideal state
Dependabot alerts, malware alerts and security updates are on; the dependency graph and review cover every manifest; updates wait their cooldown, then merge within days.
| Part | Ideal | Set up |
|---|---|---|
| Dependabot alerts | Vulnerability and malware alerts on; no malware alert open; no vulnerability alert older than a week | Enable both in the organization's security configuration; malware alerts are off until asked for |
| Dependency updates | Security fixes arrive grouped; a new release waits 14 days; packages come from one trusted registry | In dependabot.yml: a cooldown, and a group that applies to security updates |
6 sources, newest 2026-11-13
- GitHub Docs: Dependabot alerts 2026-11-13
- GitHub Docs: Dependabot malware alerts 2026-11-13
- GitHub Docs: Dependabot security updates 2026-11-13
- GitHub Docs: Dependabot version updates 2026-11-13
- GitHub Docs: Dependency graph 2026-11-13
- GitHub Docs: Dependency review 2026-11-13
Worst gaps
- 1Direct dependencies on the latest allowed60%40 pts under goal
- 2Adopting repos within the cooldown of the newest tag0%100 pts under goal
- 3Actions pinned to the latest allowed90.9%9.1 pts under goal
- 4Open dependency PRs2 PRs1 PRs over goal
Direct dependencies on the latest allowed
| Package | Used in | Installed | Latest allowed | Newest | Status | Majors behind | Waiting |
|---|---|---|---|---|---|---|---|
| knip | . | 6.44.0 | 6.44.2 | 6.47.0 | behind | – | 7 days |
| playwright-core | . | 1.64.1 | 1.65.0 | 1.65.1 | behind | – | 1 days |
| axe-core | . | 4.14.0 | 4.14.0 | 4.14.1 | current | – | – |
| typescript | . | 6.0.3 | 6.0.3 | 6.0.3 | current | – | – |
| yaml | . | 2.9.1 | 2.9.1 | 2.9.1 | current | – | – |
Quality
No open alert or malware, every dependency and action on its newest allowed release, packages only from trusted registries.
GitHub features100
Dependabot alerts1 on/offgoal ≥ 1
Whether GitHub warns when a library the repo uses has a known vulnerability; on is better.
gh api graphql: repository.hasVulnerabilityAlertsEnabled read 2026-11-21 13:37 UTC
Goal: GitHub docs, About Dependabot alerts
Open findings100
Open Dependabot vulnerabilities0 alertsgoal ≤ 0
Known vulnerabilities in the libraries the repo uses that are not fixed yet, by severity; fewer is better.
| critical | 0 alerts | |
|---|---|---|
| high | 0 alerts | |
| medium | 0 alerts | |
| low | 0 alerts |
gh api repos/SoulCraft-Org/git-crafter/dependabot/alerts --paginate (open alerts that are vulnerabilities, by security_advisory.severity; malware left out) read 2026-11-21 13:37 UTC
Goal: GitHub docs, About Dependabot alerts: each alert is a known vulnerability in a dependency; template goal: none left open
Open malware alerts0 alertsgoal ≤ 0
Libraries the repo uses that GitHub flags as malware; none is the only safe number.
gh api repos/SoulCraft-Org/git-crafter/dependabot/alerts --paginate (open alerts whose security_advisory.classification is malware) read 2026-11-21 13:37 UTC
Goal: GitHub docs, Dependabot malware alerts (read 2026-11-10): an alert means a dependency is a known malicious package; template goal: none open
Supply chain100
Dependabot updates with a cooldown100%goal ≥ 100
Share of Dependabot update feeds that wait before taking a new release, so a bad one is caught first; higher is better.
| github-actions / | 14 days |
|---|---|
| npm / | 14 days |
.github/dependabot.yml: updates[].cooldown, the shortest of default-days and semver-*-days, against params.cooldown_days read 2026-11-21 13:37 UTC
Goal: GitHub docs, Dependabot options reference: cooldown; template goal: at least params.cooldown_days (14), long enough for a malicious release to be reported and pulled
Lockfile packages younger than the cooldown0 packagesgoal ≤ 0
Installed packages, deep ones too, published too recently to trust yet; Dependabot's cooldown covers only direct ones.
| entries added within the cooldown | 66 |
|---|---|
| downloads asked for Last-Modified (no body) | 66 |
| full documents fetched to confirm | 0 |
package-lock.json at the root against itself params.cooldown_days ago (git); for each entry added since on an allowed registry, a HEAD of its download for Last-Modified, then the registry's full document only where that is recent; no redirects, at most params.max_registry_reads requests read 2026-11-21 13:37 UTC
Goal: template goal: no package younger than params.cooldown_days (14), the same wait as security.dependabot_cooldown, applied to every lockfile entry
Repo100
Dependabot security updates on1 on/offgoal ≥ 1
Whether GitHub automatically proposes fixes for security holes in our libraries; on is better.
gh api repos/SoulCraft-Org/git-crafter (security_and_analysis.dependabot_security_updates) read 2026-11-21 13:37 UTC
Goal: GitHub docs, About Dependabot security updates
Versions63
Dependencies a major behind0 dependenciesgoal ≤ 0
Direct dependencies whose newest allowed release is a newer major, less a major a Dependabot ignore holds.
package.json (root and workspaces) and package-lock.json against npm view <name> time --json; eligible is the newest stable release at least 14 days old (params.release_age_days); direct dependencies whose eligible release is a newer major, less a major held by a Dependabot ignore (typescript) read 2026-11-21 13:37 UTC
Goal: template goal, no public benchmark: no direct dependency a major release behind its newest allowed one; near band: template default
CI's Node is the current LTS1goal ≥ 1
1 when every setup-node step in the workflows asks for the newest LTS line; with none, the .nvmrc or .node-version.
| cloud-test.yml:49: .nvmrc 26 | 26 |
|---|---|
| pages.yml:194: .nvmrc 26 | 26 |
| pages.yml:234: .nvmrc 26 | 26 |
| pages.yml:267: .nvmrc 26 | 26 |
| pages.yml:303: .nvmrc 26 | 26 |
| pages.yml:366: .nvmrc 26 | 26 |
| pages.yml:414: .nvmrc 26 | 26 |
| pages.yml:603: .nvmrc 26 | 26 |
| Current LTS line | 26 |
each actions/setup-node step's node-version or node-version-file in .github/workflows (8) against https://nodejs.org/dist/index.json, the newest line with an LTS codename read 2026-11-21 13:37 UTC
Goal: goal from Node.js, which recommends LTS releases for production (nodejs.org/en/about/previous-releases)
Adoption0
Speed
An allowed update waits days, not weeks, and its pull request merges within the week.
Queue100
Open Dependabot PRs2 PRsgoal ≤ 2
Automatic proposals to update our libraries that nobody has accepted yet; fewer is better.
| javascript | 1 PRs | |
|---|---|---|
| github_actions | 1 PRs |
gh api graphql: open pullRequests (author dependabot, labels) read 2026-11-21 13:37 UTC
Goal: template goal: dependency updates merge as they arrive
Waits100
Dependabot updates grouped100%goal ≥ 100
Share of automatic update feeds that bundle their changes into fewer proposals; higher is better.
| github-actions | 1 |
|---|---|
| npm | 1 |
.github/dependabot.yml (updates[].groups) read 2026-11-21 13:37 UTC
Goal: GitHub docs, Optimizing the creation of pull requests for Dependabot version updates: groups combine updates into fewer pull requests
Updates83
Open dependency PRs2 PRsgoal ≤ 1
Pull requests labeled as dependency updates that are open now.
Gap: 1 PRs over goal
| #148 Bump anthropics/claude-code-action from 1.0.264 to 1.0.268 in the actions g | 2 days | |
|---|---|---|
| #147 Bump knip from 6.44.0 to 6.44.1 in the npm group | 2 days |
gh pr list -R SoulCraft-Org/git-crafter --label dependencies (params.dependency_label; Dependabot's default label) --state open read 2026-11-21 13:37 UTC
Goal: template goal, no public benchmark: one grouped update PR at a time; near is Dependabot's default open-pull-requests-limit, five ("If five pull requests with version updates are open, no further pull requests are raised", docs.github.com/en/code-security/dependabot/working-with-dependabot/dependabot-options-reference, read 2026-11-03)
Oldest update waiting7 daysgoal ≤ 7
Days since the oldest pending update to a direct dependency became old enough to take; 0 when none waits.
| knip 6.44.0 → 6.44.2 | 7 days | |
|---|---|---|
| playwright-core 1.64.1 → 1.65.0 | 1 days |
package.json (root and workspaces) and package-lock.json against npm view <name> time --json; eligible is the newest stable release at least 14 days old (params.release_age_days); days since the first update past each installed version cleared the 14-day rule, the longest; 0 when none waits read 2026-11-21 13:37 UTC
Goal: template goal, no public benchmark: a weekly update run lands an allowed update within a week; near: two weeks
Oldest open dependency PR2 daysgoal ≤ 7
Days the oldest open dependency PR has waited; 0 when none is open.
| #148 Bump anthropics/claude-code-action from 1.0.264 to 1.0.268 in the actions g | 2 days | |
|---|---|---|
| #147 Bump knip from 6.44.0 to 6.44.1 in the npm group | 2 days |
gh pr list -R SoulCraft-Org/git-crafter --label dependencies (params.dependency_label; Dependabot's default label) --state open; days since the oldest opened, 0 when none is open read 2026-11-21 13:37 UTC
Goal: template goal, no public benchmark: a weekly update PR merges within its week; near: two weeks
Install100
Install step time, latest main run2 sgoal ≤ 60
Seconds the slowest dependency install step took in the newest successful push run on main.
| ci / short | 2 s | |
|---|---|---|
| ci / standard | 1 s |
latest: the newest successful push run of any workflow on main with an install step (npm ci, pnpm install or yarn install), the slowest such step (gh api actions/runs and runs/{id}/jobs); run 43744847284 (166d3a3) read 2026-11-21 13:37 UTC
Goal: template goal, no public benchmark: an install with the package cache restored (setup-node's cache input) should take under a minute
Consumption
Update pull requests and installs bill few CI minutes.
Use–
CI minutes on the latest dependency PR–goal ≤ 60
Billed Actions minutes on the newest merged dependency PR, read now.
no merged PR labeled dependencies yet
the last 10 merged PRs labeled dependencies: gh api actions/runs?head_sha=<PR head>&event=pull_request and runs/{id}/jobs, each job rounded up to the whole minute as GitHub bills it (docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions); N = 10 (params.last_n)
Goal: template goal, no public benchmark: set 2026-11-04; an update PR runs the repo's CI once or twice; near band: template default
Scanning
Quality
100
4 of 4 measured
Speed
–
0 of 0 measured
Consumption
100
1 of 1 measured
Ideal state
Code scanning default setup and secret scanning with push protection are on; no alert stays open, and the scans run in minutes.
| Part | Ideal | Set up |
|---|---|---|
| Secret scanning | Bought: scanning and push protection on. Free: a secret scan that must pass to merge | Enable Secret Protection, or require a pinned scanner's check in a ruleset |
| Code scanning | Code scanning on where the repo is public or Code Security is bought; never billed unasked | Enable CodeQL default setup in the repo security settings |
4 sources, newest 2026-11-13
- GitHub Docs: Code scanning 2026-11-13
- GitHub Docs: Configuring default setup for code scanning 2026-11-13
- GitHub Docs: Secret scanning 2026-11-13
- GitHub Docs: Push protection 2026-11-13
Quality
Both scans on, and no open code scanning or secret scanning alert.
GitHub features100
Code scanning1 on/offgoal ≥ 1
Whether GitHub scans the repo's own code for vulnerabilities and errors; on is better, even where it costs.
gh api repos/SoulCraft-Org/git-crafter/code-scanning/default-setup (state) and code-scanning/analyses read 2026-11-21 13:37 UTC
Goal: GitHub docs, About code scanning
Secret scanning and push protection1 on/offgoal ≥ 1
Whether GitHub finds secrets in the repo and blocks pushes that hold one; both on is better, even where it costs.
| secret scanning | 1 |
|---|---|
| push protection | 1 |
gh api repos/SoulCraft-Org/git-crafter (security_and_analysis: secret_scanning and secret_scanning_push_protection) read 2026-11-21 13:37 UTC
Goal: GitHub docs, About secret scanning, and About push protection
Open findings100
Open code scanning alerts0 alertsgoal ≤ 0
Problems code scanning found in the repo's own code that are not fixed yet; not counted while it is off.
| critical | 0 alerts | |
|---|---|---|
| high | 0 alerts | |
| medium | 0 alerts | |
| low | 0 alerts |
gh api repos/SoulCraft-Org/git-crafter/code-scanning/alerts --paginate (open alerts, by rule.security_severity_level or rule.severity) read 2026-11-21 13:37 UTC
Goal: GitHub docs, About code scanning alerts; template goal: none open
Open secret scanning alerts0 alertsgoal ≤ 0
Secrets found in the repo that are not revoked yet; not counted while secret scanning is off.
gh api repos/SoulCraft-Org/git-crafter/secret-scanning/alerts --paginate (open alerts, by secret_type_display_name) read 2026-11-21 13:37 UTC
Goal: GitHub docs, About secret scanning: a leaked secret should be revoked; template goal: none open
Speed
No speed metric yet.
Consumption
The latest scans bill few runner minutes.
Cost100
Runner minutes, the latest security scans4 minutesgoal ≤ 5
Billed runner minutes the latest run of each security scan workflow took; the scans still run on every change
| secret-scan | 0 minutes | |
|---|---|---|
| CodeQL | 4 minutes |
latest: gh api actions/runs/{id}/jobs: each workflow named like params.security_workflows, the repo's own (its latest run that did real work, of its newest 10 of the last 20 runs per workflow) and GitHub's dynamic ones such as CodeQL default setup (its latest passed run), less CodeQL - Code Quality; billed runner minutes, summed read 2026-11-21 13:37 UTC
Goal: template goal (2026-11-03): the scans on one change bill at most 5 runner minutes, half the ten-minute build (Kent Beck, Extreme Programming Explained, 2nd edition, 2004)
Insights
Quality
100
1 of 1 measured
Speed
0
1 of 1 measured
Consumption
100
1 of 1 measured
Ideal state
A healthy repo shows it in Insights: every health file present, no finished branch left behind, and few runner minutes wasted.
| Part | Ideal | Set up |
|---|---|---|
| Pulse, Commits, Code frequency | Work lands as small merged pull requests, few stay open, and issues close as fast as they open | Scored on the Pull requests, Issues and Code tabs; the code frequency API refuses a repo of 10,000 commits |
| Contributors | Every default-branch commit is credited to an account; a count of activity is no measure of a person | Link each commit email to an account; Claude Code contribution metrics credit agent work once turned on. Not scored: it rarely moves |
| Community | The health checklist is complete | Add a README, license, contributing guide, code of conduct, issue forms and a pull request template |
| Traffic and Forks | Not scored: no documented practice sets a goal for views, clones or forks | Traffic keeps 14 days and needs an admin token; its clones mostly count workflow checkouts |
| Dependency graph | Every manifest parses, so every dependency is known | Keep the graph on and commit lock files in a format it reads. Not scored: it rarely moves, and Security scores the alerts |
| Network | Only the default branch and live work remain; a leftover branch is gone within a day | Turn on automatic branch deletion; delete the branch of a pull request closed without merging; open a pull request within a day |
| People | Everyone with write access has committed within 90 days | Review the people list each quarter and remove access nobody uses |
| Actions metrics | Under a tenth of billed minutes buys nothing; a check failing a pull request is not waste | GitHub offers no API for these two views; both are computed from workflow runs and jobs |
16 sources, newest 2026-11-10
- GitHub Docs: About repository graphs 2026-11-10
- GitHub Docs: About community profiles for public repositories 2026-11-10
- GitHub Docs: Viewing a project's contributors 2026-11-10
- GitHub Docs: Dependency graph 2026-11-10
- GitHub Docs: Managing the automatic deletion of branches 2026-11-10
- GitHub Docs: Viewing people with access to your repository 2026-11-10
- Microsoft Learn: Microsoft cloud security benchmark, Privileged Access (PA-4) 2026-11-10
- GitHub Docs: About GitHub Actions metrics 2026-11-10
- GitHub Docs: REST API endpoints for repository traffic 2026-11-10
- DORA: DORA's software delivery performance metrics 2026-11-10
- Claude Code Docs: Claude Code GitHub Actions 2026-11-10
- Anthropic: Measuring AI agent autonomy in practice 2026-11-10
- Microsoft Research: The SPACE of Developer Productivity: There's more to it than you think 2021-02-01
- GitHub Docs: REST API endpoints for repository statistics 2026-11-10
- Claude Code Docs: Track team usage with analytics 2026-11-10
- GitHub: Engineering System Success Playbook 2025-05-01
Quality
The health checklist is complete, no branch outlives its pull request, and access nobody uses is removed.
Community100
Community health checklist100%goal ≥ 100
GitHub's own score for the health files a repo should have: README, license, contributing, code of conduct, templates
| Description | 1 | |
|---|---|---|
| README | 1 | |
| License | 1 | |
| Contributing guide | 1 | |
| Code of conduct | 1 | |
| Pull request template | 1 |
state: gh api repos/SoulCraft-Org/git-crafter/community/profile, GitHub's health percentage and the files it found read 2026-11-21 13:37 UTC
Goal: GitHub docs, About community profiles for public repositories and REST community metrics (read 2026-11-10): the checklist names the recommended files and the API scores how many are present; goal: all of them
Speed
A leftover branch is gone within a day of its pull request closing.
Network0
Oldest leftover branch189 hoursgoal ≤ 24
Hours the oldest leftover branch has waited since its pull request closed, or since its last commit; 0 when none
Gap: 165 hours over goal
| leftover branches | 1 |
|---|
state: GraphQL refs under refs/heads (the first 1000) with their pull requests: a branch whose pull request closed or merged, or one older than params.branch_grace_hours with none; the default branch, open pull requests and params.keep_branches do not count; each timed from its pull request's close, or from its last commit read 2026-11-21 13:37 UTC
Goal: template goal (2026-11-10): a finished branch is gone within a day, near three; GitHub docs, Managing the automatic deletion of branches: a merged pull request's branch can go at once, so only closed and never-proposed ones wait
Consumption
At most a tenth of billed runner minutes goes to runs that are cancelled, time out or fail after merge.
Actions usage100
Settings
Quality
100
5 of 7 measured
Speed
100
1 of 2 measured
Consumption
–
0 of 1 measured
Ideal state
Settings hold their documented best values: rules no one can bypass, least access, no unused credential, no wait for a person, nothing billed unasked.
| Part | Ideal | Set up |
|---|---|---|
| General | One merge method, auto-merge off, merged branches deleted, no wiki, forking off for a private repo | Set them once on the General page, then name the values in the repo's targets so drift is counted |
| Access | Members only via the org: no outside collaborator, invite or custom role. A public repo gates fork runs, takes private reports, blocks secrets, has Discussions | Org base permission read, two-factor on; invite to the org, not a repo; public repo settings: templates/open/README.md |
| Rules, branches and tags | Rulesets: a pull request and a passing check to merge, no force push, deletion or bypass, tags fixed; custom properties only to target rulesets | An organization ruleset for every default branch; repo rulesets for checks, tags and secret file names |
| Actions and webhooks | Only selected actions, pinned to a commit, a read-only token, no fork runs; each webhook has a secret and checks SSL | Actions page: policies and workflow permissions, scored on the Security and Actions tabs; add a webhook only with a secret |
| Copilot, Planning, Codespaces | Copilot review and Codespaces off unless bought: both bill by use; issue types and fields set once for the organization | Leave both off; planning lives in organization settings and is scored on the Issues and Projects tabs |
| Environments and Pages | Each environment deploys from named branches only, with no reviewer or timer; Pages is private, built by a workflow, over HTTPS | Environment page: selected branches and tags; Pages page: source GitHub Actions, visibility private |
| Security and secrets | Free features on: dependency graph, Dependabot alerts and security updates; no deploy key; every stored secret read by a workflow | One organization security configuration; paid scanning only when bought; delete a secret when its workflow goes |
| Apps and autolinks | Only apps the organization uses, each with the permissions it needs; autolinks only for a tracker outside GitHub | Review installed apps on the organization's GitHub Apps page; add one autolink per outside ticket prefix |
25 sources, newest 2026-11-12
- GitHub docs: About rulesets 2026-11-10
- GitHub docs: Available rules for rulesets 2026-11-10
- GitHub docs: REST API endpoints for rules 2026-11-10
- GitHub docs: REST API endpoints for repositories, Get a repository 2026-11-10
- GitHub docs: About merge methods on GitHub 2026-11-10
- GitHub docs: Managing the automatic deletion of branches 2026-11-10
- GitHub docs: Setting base permissions for an organization 2026-11-10
- GitHub docs: Requiring two-factor authentication in your organization 2026-11-10
- GitHub docs: Managing custom properties for repositories in your organization 2026-11-10
- GitHub docs: Managing GitHub Actions settings for a repository 2026-11-10
- GitHub docs: Secure use reference, audit and rotate registered secrets 2026-11-10
- GitHub docs: Deployments and environments 2026-11-10
- GitHub docs: Best practices for using webhooks 2026-11-10
- GitHub docs: Managing deploy keys 2026-11-10
- GitHub docs: About GitHub Advanced Security, what a private repo pays for 2026-11-10
- GitHub docs: GitHub Actions billing 2026-11-10
- GitHub changelog: Copilot code review will start consuming GitHub Actions minutes 2026-04-27
- Microsoft Learn: Secure the developer environment for Zero Trust 2026-03-26
- Microsoft Azure Verified Modules: TFNFR3, GitHub repo branch protection 2025-11-19
- Anthropic: Claude Code GitHub Actions, the Claude GitHub App and its permissions 2026-11-10
- Anthropic: Claude Code, Code Review 2026-10-24
- Anthropic: Use Claude Code in the cloud 2026-11-10
- OpenSSF Scorecard: checks 2026-10-28
- GitHub Docs: Approving workflow runs from forks 2026-11-12
- GitHub Docs: Configuring private vulnerability reporting for a repository 2026-11-12
Quality
Branch, tags and deploys are protected with no bypass, secret files cannot be pushed, access stays inside the organization, and every secret is used.
Rules100
Default branch rules1 on/offgoal ≥ 1
Whether the default branch requires a pull request and blocks force pushes and deletion; on is better.
| requires a pull request | 1 |
|---|---|
| blocks force pushes | 1 |
| blocks deletion | 1 |
| ruleset rules on the default branch | 5 |
gh api repos/SoulCraft-Org/git-crafter/branches/{branch}/protection and repos/SoulCraft-Org/git-crafter/rules/branches/{branch}, {branch} the default branch: a pull request required, force pushes blocked, deletion blocked read 2026-11-21 13:37 UTC
Goal: GitHub docs, Available rules for rulesets: Require a pull request before merging, Block force pushes, Restrict deletions
Required status checks1 checksgoal ≥ 1
How many automatic checks must pass before a change can join the default branch; more is better.
| ci / ci-ok | 1 |
|---|
gh api repos/SoulCraft-Org/git-crafter/branches/{branch}/protection and repos/SoulCraft-Org/git-crafter/rules/branches/{branch} (required_status_checks), {branch} the default branch read 2026-11-21 13:37 UTC
Goal: GitHub docs, About protected branches: Require status checks before merging; one required check at least
Protections missing–goal ≤ 0
Guards that are off: rules with no bypass, fixed tags, a push rule on secret file names, deploys from named branches.
a ruleset's bypass list is hidden from this token: needs an admin token; refreshed by a --local collect run
state: gh api repos/SoulCraft-Org/git-crafter/rulesets and each active one (bypass_actors, tag rules deletion and update, push rule file_path_restriction against params.blocked_paths), branches/the default branch/protection (enforce_admins), tags (the first listed), environments (deployment_branch_policy); a row with nothing to guard is left out
Goal: GitHub docs, About rulesets (bypass lists), Available rules for rulesets (Restrict updates, Restrict deletions, Restrict file paths) and Deployments and environments (deployment branches and tags), read 2026-11-10; goal: none missing
Repo–
General settings off standard–goal ≤ 0
Settings on the General page that differ from the values this repo names as its standard.
gh api repos answered without allow_squash_merge: needs an admin token; refreshed by a --local collect run
state: gh api repos/SoulCraft-Org/git-crafter, each field named in params.expected against its value there
Goal: template goal: a repo names the General settings it holds itself to and none drifts; GitHub docs, REST API endpoints for repositories, Get a repository, lists the fields (read 2026-11-10)
Access100
Outside access0 peoplegoal ≤ 0
People outside the organization who can reach the repo, plus invitations not yet accepted.
| outside collaborators | 0 |
|---|---|
| pending invitations | 0 |
state: gh api repos/SoulCraft-Org/git-crafter/collaborators?affiliation=outside and repos/SoulCraft-Org/git-crafter/invitations, counted read 2026-11-21 13:37 UTC
Goal: template goal: access comes through organization membership, so no one holds it from outside and no invitation stays open; a repo with outside collaborators sets its own goal
Secrets no workflow reads0 secretsgoal ≤ 0
Stored Actions secrets whose name no workflow file uses; each is a credential kept for nothing.
| secrets stored | 1 |
|---|---|
| read by a workflow | 1 |
state: gh api repos/SoulCraft-Org/git-crafter/actions/secrets and each environment's secrets (names only), against secrets.NAME in .github/workflows/*.yml of the checkout read 2026-11-21 13:37 UTC
Goal: GitHub docs, Secure use reference, Audit and rotate registered secrets (read 2026-11-10): review the registered secrets and remove those no longer needed
Open-repo settings off0 settingsgoal ≤ 0
Settings a public repo needs: fork run approval, private vulnerability reporting, push protection, Discussions.
| Every outside contributor's run waits for approval | 1 |
|---|---|
| Private vulnerability reporting is on | 1 |
| Secret scanning push protection is on | 1 |
| Discussions are on, for ideas before issues | 1 |
state: gh api repos/SoulCraft-Org/git-crafter (has_discussions, security_and_analysis.secret_scanning_push_protection), repos/SoulCraft-Org/git-crafter/actions/permissions/fork-pr-contributor-approval (approval_policy) and repos/SoulCraft-Org/git-crafter/private-vulnerability-reporting (enabled); not measured for a private repo read 2026-11-21 13:37 UTC
Goal: template goal: each is one API call and protects the repo from outside code or a public leak; GitHub docs, Approving workflow runs from forks, Configuring private vulnerability reporting, About push protection and Enabling GitHub Discussions (read 2026-11-12)
Speed
No rule waits for a person or a timer, and dependency updates arrive grouped.
Waits100
Rules that wait for a person0 rulesgoal ≤ 0
Merge and deploy rules that need a person's approval or a timer before work can land.
| rules requiring an approval | 0 |
|---|---|
| rules requiring a code owner's review | 0 |
| rules requiring approval of the last push | 0 |
| rules naming required reviewers | 0 |
| environments with required reviewers | 0 |
| environments with a wait timer | 0 |
state: pull_request rules of the active rulesets on the default branch and of branches/the default branch/protection (approvals, code owner review, last-push approval, required reviewers), and each environment's protection_rules (required_reviewers, wait_timer) read 2026-11-21 13:37 UTC
Goal: template goal: no person reviews, so a rule that waits for one stops every merge or deploy; a repo with human reviewers drops this metric. GitHub docs, Available rules for rulesets and Deployments and environments, name the rules (read 2026-11-10)
Age of the admin readings–goal ≤ 24
Hours since a signed-in run last read the settings an automatic run cannot; an old reading can hide a changed setting.
no signed-in run is recorded yet: run collect.mjs --local
state: generated_at of local.json in the repo's data folder, the last collect.mjs --local run, against the time of this run
Goal: template goal, no public benchmark: a setting changed today shows on the page by tomorrow, so the signed-in run that reads these settings is at most a day old
Consumption
No setting bills past what the plan includes unless it was bought on purpose.
Cost–
Settings that bill past the plan–goal ≤ 0
Settings switched on that add charges beyond what the plan includes.
a public repo is not billed for Actions cache or a Copilot review, so nothing here can bill it
state: gh api repos/SoulCraft-Org/git-crafter/actions/cache/storage-limit (max_cache_size_gb against params.included_cache_gb) and the active rulesets' copilot_code_review rules; not measured for a public repo
Goal: GitHub docs, GitHub Actions billing (read 2026-11-10): cache storage past the included 10 GB a repo is billed; GitHub changelog, 2026-04-27: Copilot code review on a private repo uses Actions minutes from 2026-06-01; goal: none on unless bought
Pages
Quality
95
11 of 13 measured
Speed
100
8 of 8 measured
Consumption
100
2 of 3 measured
Ideal state
The site builds and deploys from a workflow on every merge, rarely fails, restores within the hour, and stays fast, readable and accessible.
4 sources, newest 2026-11-13
Worst gaps
- 1Reading grade, hardest page9.3 grade0.3 grade over goal
Failed deploys, last 10
| 2026-11-20 14:12 | 0 merges | |
|---|---|---|
| 2026-11-19 14:34 | 0 merges | |
| 2026-11-18 14:22 | 0 merges | |
| 2026-11-17 14:44 | 0 merges | |
| 2026-11-16 13:52 | 0 merges | |
| 2026-11-15 18:08 | 7 merges | |
| 2026-11-15 12:53 | 0 merges | |
| 2026-11-14 12:21 | 0 merges | |
| 2026-11-14 04:58 | 1 merges | |
| 2026-11-14 04:35 | 1 merges |
| Deployed (UTC) | Commit | Commit known by | Merges shipped | Median lead time | Result | Restored after |
|---|---|---|---|---|---|---|
| 2026-11-20 14:12 | 166d3a3 | – | 0 | – | no fix needed | – |
| 2026-11-19 14:34 | 166d3a3 | – | 0 | – | no fix needed | – |
| 2026-11-18 14:22 | 166d3a3 | – | 0 | – | no fix needed | – |
| 2026-11-17 14:44 | 166d3a3 | – | 0 | – | no fix needed | – |
| 2026-11-16 13:52 | 166d3a3 | – | 0 | – | no fix needed | – |
| 2026-11-15 18:08 | 166d3a3 | – | 7 | 0.1 h | no fix needed | – |
| 2026-11-15 12:53 | 8023bd4 | – | 0 | – | no fix needed | – |
| 2026-11-14 12:21 | 8023bd4 | – | 0 | – | no fix needed | – |
| 2026-11-14 04:58 | 8023bd4 | – | 1 | 0 h | no fix needed | – |
| 2026-11-14 04:35 | c267bc4 | – | 1 | 0 h | no fix needed | – |
Quality
Pages draw only from design tokens, pass contrast and axe, and every deploy passes its checks.
Reading grade, hardest page9.3 gradegoal ≤ 9
The school grade needed to read the hardest page; a lower grade is easier for everyone, so lower is better.
Gap: 0.3 grade over goal
| / | 9.3 grade | |
|---|---|---|
| /metrics.html | 7.1 grade |
Playwright (Chrome) on https://static.invalid, key pages at 1280 px: Flesch-Kincaid grade of the main element's prose (lines ending in sentence punctuation); value is the hardest page read 2026-11-21 13:37 UTC
Goal: goal: WCAG 2.2 Success Criterion 3.1.5 Reading Level (AAA) asks for text a reader with lower secondary education reads, seven to nine years of school (w3.org/WAI/WCAG22/Understanding/reading-level, updated 2026-06-28, read 2026-11-10); grade 9 is its top. The near band is a Git Crafter default
Raw hex outside tokens0 valuesgoal ≤ 0
Colors typed straight into the code instead of taken from the brand palette; fewer is better.
regex over pages, quality/render (.css) with comments stripped; excludes quality/render/tokens.css: the token file that defines every color read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: every color comes from the design tokens (params.tokens), the one source of the palette. The Design Tokens Format Module 2025.10 shares tokens across disciplines, tools and technologies (designtokens.org/tr/2025.10/format, 2025-10-28, read 2026-11-10); zero is a Git Crafter default
Raw px outside tokens0 valuesgoal ≤ 0
Fixed sizes typed straight into the code instead of taken from the shared scale; fewer is better.
regex over pages, quality/render (.css) with comments stripped; excludes quality/render/tokens.css: the token file that defines every color read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: every size comes from the token scale. The Design Tokens Format Module 2025.10 shares tokens across disciplines, tools and technologies (designtokens.org/tr/2025.10/format, 2025-10-28, read 2026-11-10); zero is a Git Crafter default; the near band is wide, since a border or an icon size often has no token
Contrast failures (axe)0 elementsgoal ≤ 0
Page elements whose text is hard to read against its background; fewer is better.
| / | 0 elements | |
|---|---|---|
| /metrics.html | 0 elements |
Playwright (Chrome) on https://static.invalid, key pages at 1280 and 375 px: axe-core 4.14.0 color-contrast, distinct failing elements per page across every width read 2026-11-21 13:37 UTC
Goal: goal: WCAG 2.2 AA, Success Criterion 1.4.3 Contrast (Minimum), as axe-core's color-contrast rule tests it (w3.org/TR/WCAG22); the near band is a Git Crafter default
Sentences over 30 words0 sentencesgoal ≤ 0
Sentences on the pages that run too long to read easily; fewer is better.
| / | 0 sentences | |
|---|---|---|
| /metrics.html | 0 sentences |
Playwright (Chrome) on https://static.invalid, key pages at 1280 px: sentences over 30 words (params.long_sentence_words) in the main element's prose read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal: no sentence on a key page over params.long_sentence_words (30) words. GOV.UK splits sentences over 25 words (guidance.publishing.service.gov.uk, Use clear language, read 2026-11-10); 30 is the looser limit Git Crafter sets for its own writing
axe violations, not contrast0 elementsgoal ≤ 0
Page elements an automatic accessibility scan flags as hard for some people to use; fewer is better.
Playwright (Chrome) on https://static.invalid, key pages at 1280 and 375 px: axe-core 4.14.0 default rules except color-contrast and target-size, distinct failing elements; detail is by rule, with its first failing element read 2026-11-21 13:37 UTC
Goal: goal: WCAG 2.2 AA as axe-core's default rules test it (w3.org/TR/WCAG22); the near band is a Git Crafter default
Small tap targets, phone width0 elementsgoal ≤ 0
Buttons and links on a phone that are too small to tap easily; fewer is better.
| / | 0 elements | |
|---|---|---|
| /metrics.html | 0 elements |
Playwright (Chrome) on https://static.invalid, key pages at 375 px: axe-core 4.14.0 target-size (WCAG 2.2 SC 2.5.8, 24 px), switched on; failing elements read 2026-11-21 13:37 UTC
Goal: goal: WCAG 2.2 AA, Success Criterion 2.5.8 Target Size (Minimum), 24 by 24 CSS px (w3.org/TR/WCAG22); the near band is a Git Crafter default
Broken internal links0 targetsgoal ≤ 0
Links inside the site that lead to a missing or failing page; fewer is better.
GET crawl of https://static.invalid from /, same origin, at most 200 fetches, /api/ and /cdn-cgi/ and /quality/ skipped (3 fetched, every reachable page): internal link targets answering 4xx or 5xx, once per target; a target that redirects off the site counts as answered, whatever the other host says; detail label is target ← first page linking it read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal, no public benchmark: every internal link answers, since a dead link ends the visitor's task
Latest deploy100
Latest deploy failed0goal ≤ 0
1 when the latest deploy was rolled back or shipped a named regression; on Pages, when its deployment failed.
| 2026-11-20 14:12 166d3a3 | 0 |
|---|
GitHub Pages: gh api repos/SoulCraft-Org/git-crafter/deployments?environment=github-pages and each deploy's statuses; a deploy failed when its newest status is failure or error; restored at the next successful deploy; the last 10 ended deploys read 2026-11-21 13:37 UTC
Goal: goal from DORA's elite band (2024 Accelerate State of DevOps Report, p. 13, dora.dev/research/2024/dora-report), a 5% change fail rate, so the latest deploy should hold
Latest failure's time to restore–goal ≤ 1
Hours from the latest failed deploy to its rollback or fix (on Pages, the next successful one); counts until restored.
none of the last 10 deploys failed, so there is nothing to restore
GitHub Pages: gh api repos/SoulCraft-Org/git-crafter/deployments?environment=github-pages and each deploy's statuses; a deploy failed when its newest status is failure or error; restored at the next successful deploy; the last 10 ended deploys
Goal: goal from DORA's elite band (2024 Accelerate State of DevOps Report, p. 13, dora.dev/research/2024/dora-report), failed deployment recovery time less than one hour. Near is the high band, less than one day
Last 10 deploys100
Failed deploys, last 100%goal ≤ 5
Share of the last 10 deploys rolled back or shipping a regression; on Pages, the github-pages deployments that failed.
GitHub Pages: gh api repos/SoulCraft-Org/git-crafter/deployments?environment=github-pages and each deploy's statuses; a deploy failed when its newest status is failure or error; restored at the next successful deploy; the last 10 ended deploys read 2026-11-21 13:37 UTC
Goal: goal from DORA's elite band (2024 Accelerate State of DevOps Report, p. 13, dora.dev/research/2024/dora-report), a 5% change fail rate. Near is the high band, 20%
Repo–
Pages visibility private–goal ≥ 1
Whether this page can be seen only by members of the repo's organization; private is better.
a public repo publishes a public Pages site: private Pages needs a private repo on GitHub Enterprise Cloud
gh api repos/SoulCraft-Org/git-crafter/pages (public); repos/SoulCraft-Org/git-crafter (private, owner type) and orgs/{owner} (plan), as only GitHub Enterprise Cloud publishes private Pages
Goal: GitHub docs, Changing the visibility of your GitHub Pages site: a private or internal repo on GitHub Enterprise Cloud can publish privately; template goal: the page shows internal data, so only members see it
Speed
A merged change is live within hours, and pages paint fast on a phone.
LCP, mobile, slowest page0.21 sgoal ≤ 2.5
How long the main content takes to appear on a phone, for the slowest page, in seconds; lower is better.
| / (lab) | 0.21 s | |
|---|---|---|
| /metrics.html (lab) | 0.18 s |
lab fallback, our numbers and not Google's: Playwright on Chromium 157.0.8103.78, one cold load per page with Lighthouse's mobile settings applied through CDP (throttling.mobileSlow4G: 4x CPU slowdown, 562.5 ms request latency, 1474.56 Kbps down, 675 Kbps up; 412 x 823 px at 1.75x), for /, /metrics.html, where PageSpeed Insights did not answer: /, /metrics.html (not a public URL (a built static site)). 2 of 2 key pages measured; value is the worst page, / (lab) read 2026-11-21 13:37 UTC
Goal: goal: a good Largest Contentful Paint is 2.5 s or less and a poor one over 4 s, per Core Web Vitals (web.dev/articles/vitals and web.dev/articles/lcp, read 2026-11-03)
CLS, mobile, worst page0 scoregoal ≤ 0.1
How much the worst page jumps around while loading on a phone; lower is better.
| / (lab) | 0 score | |
|---|---|---|
| /metrics.html (lab) | 0 score |
lab fallback, our numbers and not Google's: Playwright on Chromium 157.0.8103.78, one cold load per page with Lighthouse's mobile settings applied through CDP (throttling.mobileSlow4G: 4x CPU slowdown, 562.5 ms request latency, 1474.56 Kbps down, 675 Kbps up; 412 x 823 px at 1.75x), for /, /metrics.html, where PageSpeed Insights did not answer: /, /metrics.html (not a public URL (a built static site)). 2 of 2 key pages measured; value is the worst page, / (lab) read 2026-11-21 13:37 UTC
Goal: goal: a good Cumulative Layout Shift is 0.1 or less and a poor one over 0.25, per Core Web Vitals (web.dev/articles/vitals and web.dev/articles/cls, read 2026-11-03)
Clicks from home, longest task1 clicksgoal ≤ 2
The most clicks from the home page that any main task needs; fewer is better.
| Read the metrics and goals | 1 clicks |
|---|
GET crawl of https://static.invalid from /, same origin, at most 200 fetches, /api/ and /cdn-cgi/ and /quality/ skipped: shortest path from / in the crawled link graph to each of params.tasks; an external goal adds the click on its link; a task with several goals takes the fewest clicks; value is the longest task read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal, no public benchmark: every main task within two clicks of the home page. Nielsen Norman Group finds no data behind a click limit and weighs clear labels and fast pages beside it (nngroup.com/articles/3-click-rule, 2019-08-11, read 2026-11-10), so this tab pairs it with keyboard_task_share and words_before_action
Words before first action12 wordsgoal ≤ 50
Words a visitor reads before the first link or button, on the wordiest page; fewer is better.
| / | 0 words | |
|---|---|---|
| /metrics.html | 12 words |
Playwright (Chrome) on https://static.invalid, key pages at 1280 px: visible words in main before its first visible link, button or field; value is the wordiest page read 2026-11-21 13:37 UTC
Goal: Git Crafter default goal, no public benchmark: a visitor reaches something to click within fifty words
TBT, mobile, slowest page0 msgoal ≤ 200
How long the slowest page freezes and ignores taps while loading on a phone; lower is better.
| / (lab) | 0 ms | |
|---|---|---|
| /metrics.html (lab) | 0 ms |
lab fallback, our numbers and not Google's: Playwright on Chromium 157.0.8103.78, one cold load per page with Lighthouse's mobile settings applied through CDP (throttling.mobileSlow4G: 4x CPU slowdown, 562.5 ms request latency, 1474.56 Kbps down, 675 Kbps up; 412 x 823 px at 1.75x), for /, /metrics.html, where PageSpeed Insights did not answer: /, /metrics.html (not a public URL (a built static site)). 2 of 2 key pages measured; value is the worst page, / (lab) read 2026-11-21 13:37 UTC
Goal: goal: a Total Blocking Time under 200 ms on average mobile hardware (web.dev, Total Blocking Time, updated 2024-11-04, read 2026-11-04); near is 500 ms, above which web.dev rates INP poor, as TBT is INP's lab stand-in (web.dev, Interaction to Next Paint, updated 2025-09-02, read 2026-11-04)
Now100
Merges waiting to deploy0 mergesgoal ≤ 0
Merges to main that change what deploys and that production does not hold right now.
GitHub Pages: gh api repos/SoulCraft-Org/git-crafter/deployments?environment=github-pages and each deploy's statuses; gh api repos/{repo}/compare/{live sha}...{branch}: merges production does not hold now, less the commit this run deploys and those before it read 2026-11-21 13:37 UTC
Goal: Git Crafter goal: pages.yml publishes on every push to main (its build job's timeout is 15 minutes), so no merge waits once its run ends; near: one or two merges inside a running publish
Oldest waiting merge0 hgoal ≤ 1
Hours the oldest merge that production does not hold has waited; 0 when none waits.
GitHub Pages: gh api repos/SoulCraft-Org/git-crafter/deployments?environment=github-pages and each deploy's statuses; gh api repos/{repo}/compare/{live sha}...{branch}: merges production does not hold now, less the commit this run deploys and those before it; hours since the oldest was merged, 0 when none waits read 2026-11-21 13:37 UTC
Goal: Git Crafter goal: pages.yml publishes on every push to main (its build job's timeout is 15 minutes), so a merge waits under an hour; near: DORA's elite lead time, one day (2024 Accelerate State of DevOps Report, p. 13)
Latest deploy100
Latest deploy's time from merge to live0.1 hgoal ≤ 1
Hours from the earliest merge the latest deploy shipped to that deploy.
| 1b12f09 | 0.1 h | |
|---|---|---|
| 4c59dc3 | 0.1 h | |
| c28faef | 0.1 h | |
| ac8ee24 | 0.1 h | |
| b8c3959 | 0.1 h | |
| e657a46 | 0.1 h | |
| 166d3a3 | 0.1 h |
GitHub Pages: gh api repos/SoulCraft-Org/git-crafter/deployments?environment=github-pages and each deploy's statuses; hours from the earliest merge the latest shipping deploy carried to that deploy going live; the deploy of 2026-11-15 18:08 (166d3a3) read 2026-11-21 13:37 UTC
Goal: Git Crafter goal: pages.yml publishes on every push to main (its build job's timeout is 15 minutes), so the latest deploy is live within an hour of its merge; near: DORA's elite lead time, one day (2024 Accelerate State of DevOps Report, p. 13)
Consumption
Pages stay light to download and deploys bill few minutes.
Total KiB, heaviest page319 KiBgoal ≤ 1,600
How much data the heaviest page downloads in all; less loads faster, so lower is better.
| /@1280 | 319 KiB | |
|---|---|---|
| /@375 | 319 KiB | |
| /metrics.html@1280 | 133 KiB | |
| /metrics.html@375 | 133 KiB |
Playwright (Chrome) on https://static.invalid, key pages at 1280 and 375 px: all response bytes (body plus headers) to the load event plus network idle, fresh context; value is the heaviest page and width read 2026-11-21 13:37 UTC
Goal: goal: Lighthouse's total-byte-weight guidance, aim below 1,600 KiB; Lighthouse flags pages over 5,000 KiB (developer.chrome.com/docs/lighthouse/performance/total-byte-weight, read 2026-11-02)
Form page KiB, heaviest form–goal ≤ 1,600
How much data a visitor downloads to open the heaviest form, where most tasks end; lower is better.
params.form_pages names no form page
params.form_pages
Goal: goal: Lighthouse total-byte-weight guidance, aim below 1,600 KiB; Lighthouse flags pages over 5,000 KiB (developer.chrome.com/docs/lighthouse/performance/total-byte-weight, read 2026-11-03), applied to the pages where tasks finish
Use100
CI minutes behind the latest deploy10 mingoal ≤ 20
Billed Actions minutes of the push to main the latest production deploy shipped, every workflow run on it.
| verify | 5 min | |
|---|---|---|
| pages | 4 min | |
| secret-scan | 1 min |
latest: every workflow run the push to main of the latest successful Pages deploy's sha started (gh api actions/runs?head_sha=&event=push, then runs/{id}/jobs), each job rounded up to the whole minute as GitHub bills it; the deploy of 2026-11-20 14:12 (166d3a3) read 2026-11-21 13:37 UTC
Goal: template goal, no public benchmark: the CI of one push to main under 20 billed minutes; near: template default, twice that