auto repo setup

Other Community

Skill notes

Entry router

Classify the request before changing anything. Do not combine modes merely because they all contain the word "setup". User outcome · Mode · First action "It won't run", missing dependency, new machine · Environment repair · Read project instructions and detect the actual stack "Sync before we work", "pull the latest" · Session routine · Use project instructions or execute the user's natural-language request

Operating principles

Do not infer competence from role. Match the user's demonstrated altitude. A collaborator can tell an agent "sync the remote first"; do not invent a launcher, shortcut, or wizard unless the user asked for one. Use the least mechanism that satisfies the outcome. Prefer, in order: direct Agent instruction → project instruction → explicit command → lifecycle

A1. Read the project map

Read only files that exist, in this order: AGENTS.md and AGENTS.override.md CLAUDE.md and scoped project rules ONBOARDING.md or the repository's named setup/runbook README.md

A2. Run a read-only capability inventory

Use the bundled scripts/check_env.py against the repository root when a Python 3.10+ runner is already available. It detects the declared ecosystem and checks only the relevant toolchain; it does not install dependencies or read secret values. If Python is itself the missing prerequisite, perform the same read-only manifest inventory directly instead of installing Python merely to run the audit.

A3. Repair the root cause

For each failed requirement: Capture the exact command, exit code, stdout, and stderr. Trace the failure to the declaring source: project guide, manifest, lockfile, configuration, or runtime log. Apply the smallest project-consistent repair.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@daymade · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python >=3.10
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview auto-repo-setup.preview
# Diagnose repeated output first

1. Enumerate project, local, user, managed, and plugin hook registrations.
2. Count matching entries; do not infer "three registrations" from three outputs.
3. Identify which root sessions, resumes, compactions, or subagents fired them.
4. Verify the event matcher and current runtime payload.
5. State the root cause before proposing a change.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.