AGENT SKILL

repo-maintainer

Audit and repair repository hygiene across artifacts, dependencies, CI, docs, Git state, and code-quality signals. Use for repository maintenance, cleanup, health checks, or pre-release hardening.

License 许可
MIT
最近更新
2026-10-22
Stars
★ 1
Forks
0

01 前言 Front Matter

name
repo-maintainer
risk
critical
source
https://github.com/Wolfe-Jam/faf-skills/tree/main/skills/repo-maintainer
license
MIT
date_added
1782864000000
description
Audit and repair repository hygiene across artifacts, dependencies, CI, docs, Git state, and code-quality signals. Use for repository maintenance, cleanup, health checks, or pre-release hardening.
source_repo
Wolfe-Jam/faf-skills
source_type
community
license_source
https://github.com/Wolfe-Jam/faf-skills/blob/main/LICENSE

03 SKILL.md 正文

Repository Maintainer

Overview

Audit repository health, apply authorized repairs narrowly, and finish through the repository's own protected workflow.

When to Use

Use when the user asks to maintain, clean, audit, harden, or prepare a repository for release. Use a more specific security, database, deployment, or release skill when that is the dominant task.

Repository Policy Gate

Before mutation:

  1. Read root and nested AGENTS.md, contributor guidance, maintainer docs, and release instructions.
  2. Inspect the current branch, worktree, staged files, remotes, default branch, and effective branch protection.
  3. Discover repository-native validation, synchronization, merge, and release commands.
  4. Preserve unrelated user work and generated outputs that are not in scope.

If the repository names a mandatory maintainer skill or guarded command, delegate to it instead of inventing a parallel branch, merge, sync, or release path. In agentic-awesome-skills, use antigravity-maintainer-batch-release and npm run merge:batch; main is pull-request-only.

The routine protected checks for agentic-awesome-skills are pr-policy, pr-evidence, source-validation, and artifact-preview. The supported AAS Core preview uses targeted unit tests plus one packed Linux/Node LTS smoke path and Workbench review. Do not resurrect the retired certified-v1 baseline, benchmark, tuning-gold, transaction-fault, race, or frozen OS/runtime matrix as routine merge gates.

Usage

1. Establish the baseline

git status --short --branch
git diff --stat
git diff --cached --stat
git remote -v
git log -5 --oneline

Record the repository's required runtime versions and test commands. Use a clean temporary clone or worktree when existing user changes cannot be isolated safely.

2. Audit independent lanes

Run independent read-only checks in parallel where possible.

Artifacts and Git hygiene

  • untracked caches, coverage, build output, editor files, and test leftovers;
  • tracked large or binary files, accidental secrets, executable-mode drift, and ignored-file gaps;
  • stale branches, detached HEAD, existing staged changes, submodules, and symlinks;
  • generated files whose ownership belongs to CI or a canonical-sync workflow.

Do not delete or rewrite history during the audit.

Dependencies and packaging

  • lockfile and manifest agreement;
  • outdated, vulnerable, duplicate, unused, or end-of-life dependencies;
  • runtime imports incorrectly placed in development dependencies;
  • clean-install, package-content, and executable-entrypoint behavior.

Treat audit-tool output as evidence to verify, not automatic permission to upgrade or remove packages.

CI and release health

  • failing, cancelled, skipped, or stale workflow runs;
  • stale, redundant, or unjustifiably broad runtime matrices and unpinned or obsolete actions;
  • required checks, branch protection, release permissions, and secret boundaries;
  • mismatch between documented and implemented release commands.

Documentation and repository metadata

  • README, changelog, version, examples, links, badges, credits, and support metadata;
  • contribution instructions and PR templates versus current CI policy;
  • generated catalog, site, or API documentation drift.

Code-quality signals

  • dead code, stale implementation markers, debug logging, commented-out code, and missing tests;
  • unsafe defaults, suppressed errors, credential exposure, and environment-specific paths.

For FAF projects only, also inspect declared .faf, .faf-dna, sync, score, and MCP contracts with the project's installed FAF commands.

3. Produce a prioritized decision set

For each finding report:

  • evidence and affected paths;
  • severity and user impact;
  • whether it is safe to fix now, needs approval, or belongs to another workflow;
  • exact validation that proves the repair.

Deduplicate symptoms with the same root cause. Do not mix optional modernization with release blockers.

4. Apply authorized repairs

Make the smallest coherent change set. Keep source and generated-file ownership separate, update tests with behavior changes, and rerun the targeted failing check after each repair group.

Never delete data, rewrite history, rotate credentials, change branch protection, or upgrade across breaking versions without explicit authorization.

5. Validate and publish safely

Run the repository's required pre-PR suite, then inspect the final diff for unrelated files and secrets. Commit on a topic branch and create a pull request when the target branch is protected.

Use required checks and the repository-native merge path. A user request to “push to main” describes the desired final state; it does not bypass branch protection. For releases, use the scripted release workflow and verify external publication rather than inferring success from a local tag.

Stop Condition

Finish when every in-scope finding is repaired or has one exact blocker, required validation passes, the remote integration path is verified when requested, and unrelated user work remains unchanged.

Limitations

  • Maintenance findings can depend on repository-specific ownership and release policy; read local instructions before acting.
  • Dependency and security scanners can produce false positives or incomplete reachability evidence.
  • This skill does not authorize destructive cleanup, branch-policy changes, direct protected-branch pushes, merges, deployments, or releases beyond the user's request.

04 同仓库更多 Skills

Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

testing-best-practices

Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

tailwindcss-development

Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

laravel-best-practices

Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

infer-conventions

Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai/rules`, resolve mixed or conflicting patterns (e.g. "are we using Form Requests or inline validation?"), or onboard agents and teammates to "how we do things here". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai/rules` files by hand.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

inertia-react-development

Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using <Link>, <Form>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.

★ 1
Hazek-dc
Hazek-dc/PresensiGuru_FaceNet_EMAR

deploying-to-cloud

Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.

★ 1