agentsclimarketplace

Triage active repos

Skill workingclassbuddha/codexmaxxing/skills/triage-active-repos

UI skills for Codex: design passes, browser automation, screenshots, responsive checks, and evidence packs.

Install
npx -y skills add workingclassbuddha/codexmaxxing --skill triage-active-repos

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Scan active local repositories, summarize dirty state, recent commits, likely canonical paths, risk level, and the safest next work slice. Use when the user asks what to work on next, asks Codex to look across projects, has duplicate repo paths, wants GitHub-ready packaging, or needs repo status before planning implementation.

SKILL.md

1.7 KB, as published. Nobody here has run it

Triage Active Repos

Use this skill before cross-repo planning or any change where the canonical project path may be ambiguous.

Workflow

  1. List candidate repos from the user's stated paths, recent Codex workspaces, ~/Documents/GitHub, ~/Desktop, and known project roots.
  2. For each candidate, inspect git status --short, current branch, recent commits, README, package files, and obvious test commands.
  3. Identify duplicates and choose a canonical path using recency, cleanest git history, explicit docs, and user naming.
  4. Classify risk: low docs/demo, medium UI/app, high runtime/protocol/auth/approvals/execution.
  5. Recommend one safe next slice with verification commands.

Output

Return:

  • repo map
  • canonical path recommendation
  • dirty-state summary
  • recent activity themes
  • duplicate/repo ambiguity
  • next slice
  • verification gate
  • stop conditions

Guardrails

  • Never revert or clean user changes while triaging.
  • Do not mix live organism/memory data with clean GitHub surfaces unless the user explicitly asks.
  • Treat runtime, approval, browser extension, signing, publishing, and filesystem-write changes as high risk.
  • If two repos could both be canonical and both are dirty, stop and ask.

Resources

  • Run scripts/repo_snapshot.sh <repo> [repo...] for a concise git snapshot.
  • Read references/repo-risk.md for the risk rubric and canonical-path heuristics.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.