SCM Repo Agent Skill

Enforces SCMessenger repository agent rules for iOS/Android log extraction and build verification.

2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/Treystu/SCMessenger --skill scm-repo-agent-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: SCM Repo Agent Skill
Source: https://github.com/Treystu/SCMessenger/tree/main/skills/scm-repo-agent
Command: npx skills add https://github.com/Treystu/SCMessenger --skill scm-repo-agent-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents repository drift and inconsistent documentation by enforcing SCMessenger’s agent rules, standardized log extraction, and required build verification on each change-bearing run.

Core Features & Use Cases

  • Rules Compliance Guardrails: Enforces strict adherence to AGENTS.md and LOG_EXTRACTION_STANDARD.md so agent actions stay consistent with project expectations.
  • Standardized Log Extraction: Requires deterministic extraction workflows using ios_extractor.py for iOS and adb_extractor.py for Android to produce comparable logs.
  • Mandatory Documentation Sync: Ensures canonical documentation and current state tracking are updated whenever changes impact behavior or outcomes.
  • Build Verification: Verifies changes with appropriate build commands before the session ends to reduce regressions.

Quick Start

Ask the agent to process a change-bearing run by extracting iOS logs with ios_extractor.py (or Android logs with adb_extractor.py), syncing the canonical documentation, and running the required build verification while following AGENTS.md and LOG_EXTRACTION_STANDARD.md.

Frequently Asked Questions about SCM Repo Agent Skill

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

FAQPage Schema
How do I automate iOS and Android log extraction for repository changes?

Automate iOS and Android log extraction by enforcing ios_extractor.py and adb_extractor.py workflows during change-bearing runs, ensuring deterministic logs that comply with repository standards.

Why does documentation drift happen after automated repository updates?

Documentation drift occurs when canonical tracking is not updated. Enforcing mandatory documentation synchronization during change-bearing runs prevents drift and maintains consistent project state tracking.

How do I verify builds before completing an automated repository run?

Verify builds by enforcing mandatory build verification checks before session completion. This reduces regressions by ensuring changes are validated with appropriate build commands prior to finalizing the run.

Does the SCM Repo Agent Skill work with both iOS and Android workflows?

Yes, it supports both iOS and Android workflows by enforcing platform-specific log extraction via ios_extractor.py and adb_extractor.py, while maintaining strict compliance with AGENTS.md rules.

What are the limitations of relying solely on repository automation without compliance guardrails?

Without compliance guardrails, repository automation risks drift, inconsistent documentation, and undetected regressions. Enforcing standardized extraction and build verification ensures changes remain compliant and consistent.