revibe-7edb16 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited revibe-7edb16 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Analyze a codebase to understand its architecture, file roles, design patterns, execution flows, and system design decisions. Returns structured insights and saves agent_context.json for persistent codebase understanding.
$ARGUMENTS contains a GitHub URL or owner/repo shorthand, use that$ARGUMENTS is empty, detect from the current directory: git remote get-url origin 2>/dev/nullConvert SSH to HTTPS if needed ([email protected]:owner/repo.git → https://github.com/owner/repo)
The user needs a REVIBE_API_KEY environment variable. Check if it's set:
echo "${REVIBE_API_KEY:-not_set}"If not set, tell the user:
You need a Revibe API key. Sign up free at https://app.revibe.codes, then go to Settings → API Keys to generate one. Then set it: export REVIBE_API_KEY=rk_live_your_key_herecurl -s -X POST "https://app-backend.revibe.codes/api/v1/analyze" \
-H "Content-Type: application/json" \
-H "X-Revibe-Key: ${REVIBE_API_KEY}" \
-d "{\"github_url\": \"GITHUB_URL_HERE\"}"If status is "completed", skip to step 5.
If status is "processing", poll every 10 seconds (max 3 minutes):
curl -s "https://app-backend.revibe.codes/api/v1/analysis/${JOB_ID}/status" \
-H "X-Revibe-Key: ${REVIBE_API_KEY}"Show progress to the user as each step completes.
Fetch the summary:
curl -s "https://app-backend.revibe.codes/api/v1/analysis/${JOB_ID}/summary" \
-H "X-Revibe-Key: ${REVIBE_API_KEY}"Display it as a formatted summary card:
Revibe Analysis: {name}
Architecture: {architecture_pattern}
Language: {language}
Size: {total_files} files
Entry point: {entry_point}
Key Modules:
{name} — {description} ({loc} LOC)
...
Patterns: {patterns}
Database: {type}, {tables} tables
Sections available: {sections_available}
Full analysis: {project_url}Always save the agent context file:
curl -s "https://app-backend.revibe.codes/api/v1/analysis/${JOB_ID}/agent-context" \
-H "X-Revibe-Key: ${REVIBE_API_KEY}" \
> agent_context.jsonTell the user: "Saved agent_context.json — this gives you structured codebase context for future tasks."
After showing the summary, offer to explore specific sections:
Fetch any section with:
curl -s "https://app-backend.revibe.codes/api/v1/analysis/${JOB_ID}/section/{section_name}" \
-H "X-Revibe-Key: ${REVIBE_API_KEY}"Section names: technical_architecture, file_roles, system_design_qa, story_flow, database_schema, concepts_explanation, modules
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.