Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 87%
Response Time: 21h
First Timer Success: 56%
Priivacy-ai/spec-kitty has a recorded first-timer success rate of 56.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Priivacy-ai/spec-kitty respond to incoming external pull requests in approximately 21.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 69.0 places Priivacy-ai/spec-kitty in the A tier.
The external contributor pull request merge rate for Priivacy-ai/spec-kitty is 87.4%, based on public PR activity from non-core contributors.
Priivacy-ai/spec-kitty does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Strict review standards in Priivacy-ai/spec-kitty. Ensure PR scope matches issue requirements closely before requesting review.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/Priivacy-ai/spec-kitty?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~14 hours (96% approval). Large PRs (>500 lines) take ~103 hours (39% approval). Keep your diff compact for rapid review.
Observed (branch missions/coreloop-proto-missions, PR #3922; found during Mission B dead-port-disposition-01M1TZVN) #3285 deleted test_a_baseline_entry_does_not_survive_its_owner and test_every_named_owner_resolves from the inert-slots owner gate. The helpers those tests used in tests/architectural/_inert_slots.py:574-629 now have zero callers. _baselines.yaml unassigned_entries has no consumer. The gate that ensured every inert-slot baseline entry has a resolving owner is therefore silently gone while its scaffolding (helpers + baseline section) remains, which is exactly the dead-port pattern Mission B was retiring. Expected / proposed fix Either restore the two owner tests (re-wiring them to the surviving helpers, adjusting for whatever #3285 changed) or delete the orphaned helpers at _inert_slots.py:574-629 and the unassigned_entries section of _baselines.yaml so the baseline file and the gate agree. Decide explicitly; do not leave the half-gate. Severity / recurrence LOW-MEDIUM (
Observed (Spec Kitty 3.2.7rc1, 2026-09-06/07, branch missions/coreloop-proto-missions, PR #3922) F-45 (CLI option consistency): spec-kitty agent profile list --mission … → "No such option: --mission", while the skill text says to pass --mission to EVERY spec-kitty command in multi-mission repos. Expected / proposed fix Accept-and-ignore --mission on mission-agnostic subcommands (or make the skill text list the exceptions). Severity / recurrence S3. Once per session; the skill instruction is contradicted by the CLI. Related #3469 OPEN (flag hints) and #3859 OPEN (unify --agent/--actor) are adjacent; neither covers --mission on mission-agnostic subcommands. Provenance Observed by an orchestrating agent (Claude Fable 5.1) driving missions fsm-write-path-integrity-01M1TZV6 and dead-port-disposition-01M1TZVN end to end; friction ledger kept out of repo; deduplicated against the tracker before filing.
Observed (Spec Kitty 3.2.7rc1, 2026-09-06/07, branch missions/coreloop-proto-missions, PR #3922) F-37 (ruff format vs lint): ci-quality.yml runs ruff format --check . but the repo's own touched files already fail it on main, so a WP cannot tell whether its new file "breaks" the gate; local guidance (CLAUDE.md) only mentions ruff check. (Reviewer finding on Mission A WP05.) Expected / proposed fix Document the ruff format --check expectation in CLAUDE.md (Code Style / Commands) next to ruff check ., or drop the check from ci-quality.yml. Severity / recurrence S3 (docs). One reviewer round-trip in Mission A; Mission B reviewers re-derived the rule. Related No existing issue (searched ruff format --check ci-quality). Provenance Observed by an orchestrating agent (Claude Fable 5.1) driving missions fsm-write-path-integrity-01M1TZV6 and dead-port-disposition-01M1TZVN end to end; friction ledger kept out of repo; deduplicated against the tracker before filing.
Observed (Spec Kitty 3.2.7rc1, 2026-09-06/07, branch missions/coreloop-proto-missions, PR #3922) F-26 (make test-fast): make test-fast shells out to uv run --frozen pytest, in tension with the standing "don't uv run in a worktree with a symlinked/hand-built venv" advice (CLAUDE.md, UI-testing section: a bare uv run re-syncs the environment and destroys a hand-built .venv). It did not re-sync in practice this time. Expected / proposed fix The make target could honour an existing .venv (.venv/bin/pytest) when present, falling back to uv run --frozen otherwise; or the CLAUDE.md guidance should say the target is safe. Severity / recurrence S3 (low priority; may be docs-only). Observed on every make test-fast run in lane worktrees. Related #1907 OPEN and #2803 OPEN are adjacent (venv hazards in lanes) but do not address the make target. Provenance Observed by an orchestrating agent (Claude Fable 5.1) driving missions fsm-write-path-integrity-01M1TZV6 and dead-port-disposition-01M1TZVN e
Observed (Spec Kitty 3.2.7rc1, 2026-09-06/07, branch missions/coreloop-proto-missions, PR #3922) F-06 (plan prompt): the plan prompt (packs/built-in/missions/mission-steps/software-dev/plan/prompt.md) claims spec-kitty agent context resolve --action plan "may already return a successful setup payload"; it does not (returns context only, no plan_file). Extra round-trip every time. F-16 (analyze prompt): packs/built-in/missions/mission-steps/software-dev/analyze/prompt.md:22,65 say the charter is at /charter/charter.md; the actual path is .kittify/charter/charter.md (CLAUDE.md, charter context and the review prompt agree). Expected / proposed fix Prompts match CLI behaviour and the real charter path: drop the setup-payload claim from the plan prompt (or make context resolve return it), and fix the two path citations in the analyze prompt. Severity / recurrence S3. Once per mission each (both missions). Related No existing issue covers either drift (searched context resolve --action pla
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to Priivacy-ai/spec-kitty, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of Priivacy-ai/spec-kitty acknowledge new external contributions in approximately 21 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 87.4% were successfully merged into the primary branch.
Priivacy-ai/spec-kitty has a recorded first-timer success rate of 56.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~21 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 69.0 places Priivacy-ai/spec-kitty in the Welcoming tier.
The external pull request merge rate is 87.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Priivacy-ai/spec-kitty does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for Priivacy-ai/spec-kitty are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.