Skip to content
TrustedSkillsbeta
Back to all skills

Contributor Codebase Analyzer

Checked
anivar·vlatest·backend·MIT

Analyzes a codebase for contributors, identifying potential issues and ensuring consistent coding standards for smoother onboarding and collaboration.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add anivar/contributor-codebase-analyzer --skill contributor-codebase-analyzer -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

anivar

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned anivar/contributor-codebase-analyzer at 6fd84dfb14.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
6fd84dfb14
Manifest
SKILL.md
Scanned
14 files, 3,553 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The anivar-contributor-codebase-analyzer skill analyzes a codebase to identify potential contributions from specific developers. It helps understand the scope and impact of individual contributors, facilitating code review processes or identifying areas for collaboration. This skill provides insights into developer activity within a project's repository.

When to use it

  • Code Review Preparation: Before reviewing a pull request, quickly assess the contributor’s past contributions to gain context.
  • Onboarding New Developers: Understand existing code ownership and identify potential mentors for new team members.
  • Identifying Code Ownership: Determine which developers are most familiar with specific parts of the codebase.
  • Collaboration Planning: Pinpoint areas where multiple contributors have worked, suggesting opportunities for joint effort or conflict resolution.

Key capabilities

  • Analyzes a codebase to identify contributions by developer.
  • Provides insights into developer activity within a repository.
  • Facilitates code review processes.

Example prompts

  • "Analyze the codebase and tell me what files John Doe has contributed to."
  • "Show me all commits made by Jane Smith in the last month."
  • “Who are the top 5 contributors to this project?”

Tips & gotchas

The skill requires access to a Git repository URL. The accuracy of the analysis depends on commit history and accurate author information within those commits.