establishing-code-ownership
establishing-code-ownership is a Codebase mapping & onboarding skill for AI agents, published by PostHog in the posthog repository on GitHub. Skillspace rates establishing-code-ownership D (65/100) and it passed the safety scan; the rating is based on static analysis only.
Determine which PostHog team owns a file, directory, or code path, or enumerate all code a team owns (via `products/*/product.yaml` and `.github/CODEOWNERS(-soft)?`). Use when assigning a reviewer, attributing a bug or slow query to a team, routing work, scoping a team-wide audit, or answering "who owns X" / "what does team Y own".
- Grade
- D
- Quality
- 65 / 100
- Safety
- Passed
- GitHub stars
- 35,560
Unproven: rated by static analysis only, not yet compared head-to-head.
Our two independent classifiers differ on this skill's category, so treat the placement as provisional.
This rating describes the version of the repository we crawled; it may have changed since, so go by its current files.
Our review
- Architecture
- 94 / 100
- Maturity
- Basic: a single SKILL.md
- Security scan
- No issues found
- License
- Not declared. Check the repository before reusing it.
- Adoption
- Adopted by 1 other repositories, in 1 collections
- Scope
- Repo-internal: written for the repository it lives in. PostHog teams, product.yaml owners and its CODEOWNERS files
Not checked yet
- Not judged on the rubric yet (not a contender in its category)
- No blind task eval yet
- Sibling files (scripts, references) not fetched; security scan covers SKILL.md only
Skillspace indexes and rates this skill; it does not host or endorse it. Run third-party skills at your own risk.