developer-trust-profile

Maintain per-developer trust profiles with versioned history to guide PR reviews.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill developer-trust-profile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer-trust-profile
Source: https://github.com/tomzx/agents/tree/main/skills/developer-trust-profile
Command: npx skills add https://github.com/tomzx/agents --skill developer-trust-profile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintain and reason about developers' PR reviews by creating per-developer trust profiles that summarize strengths, weaknesses, and review history.

Core Features & Use Cases

  • View or create developer trust profiles to guide future reviews.
  • Update profiles after PR reviews with summarized observations and a running history.
  • Store profiles locally at ~/.developer-trust and version them with git.

Quick Start

Create or update a GitHub developer trust profile by running /developer-trust-profile <github_username> and optionally pass --after-review <owner/repo> <pr_number> <approved|not_approved> to record a review outcome.

Frequently Asked Questions about developer-trust-profile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track developer trust levels for GitHub PR reviews?

Track developer trust levels by maintaining per-developer profiles that summarize PR review history, strengths, and weaknesses. These profiles guide future code reviews by providing structured trust level taxonomy and update logic.

What is a developer trust profile and how does it guide code review?

A developer trust profile is a local record of a developer's PR review outcomes and observations. It guides code review by maintaining a running history and structured trust taxonomy to evaluate reviewer reliability.

How do I create or update a GitHub developer trust profile after a PR review?

Create or update a GitHub developer trust profile by running the profile command with a GitHub username. Append review outcomes using the after-review flag with owner, repo, PR number, and approval status to record observations.

Does this developer trust profile skill work across multiple GitHub repositories?

Yes, the developer trust profile skill works across multiple GitHub repositories. It maintains local profile storage at the designated dotfile directory and versions the history with git to track reviews globally.

Where are developer trust profiles stored and are they versioned?

Developer trust profiles are stored locally in a dedicated dotfile directory and are fully versioned with git. This local storage approach ensures profile history is tracked and can be reviewed offline.

When should I use an automated developer trust profile instead of manual review notes?

Use an automated developer trust profile when your team needs versioned history and structured trust level taxonomy across multiple repositories. It replaces manual notes by automatically updating per-developer profiles as PR reviews occur.