repo-quality-system-lifecycle

Audit and establish quality contracts for agent-operated engineering repositories.

2|Updated Aug 15, 2026
One-click install
npx skills add https://github.com/Arenukvern/shortly --skill repo-quality-system-lifecycle-arenukvern
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-quality-system-lifecycle
Source: https://github.com/Arenukvern/shortly/tree/main/.agents/skills/repo-quality-system-lifecycle
Command: npx skills add https://github.com/Arenukvern/shortly --skill repo-quality-system-lifecycle-arenukvern

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agent-operated repositories often lack the charter clarity, validation gates, evidence paths, and safety policies that let humans and AI agents work without hidden local context. This Skill provides a structured lifecycle for establishing or auditing that structural quality contract across any repo archetype. ## Core Features & Use Cases - Repo Classification & Baseline: Classify a repository as app, library, CLI/tool, plugin, harness, or meta repo, then establish the minimum stewardship baseline (charter, agent map, docs map, validation command, release path). - Quality Contract & Honest Proof: Define the smallest checkable contract covering quality gates, evidence, decisions, safety, and handoff, and prove claims with the weakest true evidence rather than the strongest desired one. - Repository Ecology Review: Run disposition passes over plans, docs, skills, schemas, tools, and evidence to decide what to keep, compress, merge, update, remove, create, or move to checks. - Use Case: An agent inherits a growing app repo with stale docs and no clear validation command. Use this Skill to classify the repo, establish the smallest stewardship baseline, and produce a disposition table without changing product code. ## Quick Start Ask the agent to audit this repository and establish the smallest stewardship baseline with a quality contract, validation command, and evidence paths.

Frequently Asked Questions about repo-quality-system-lifecycle

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

FAQPage Schema
How do I set up a stewardship baseline for an agent-operated repository?▼

Classify the repo archetype first, then establish the minimum map: a charter or North Star, an agent map, a claims and evidence router, a docs map, one native validation command, and a release path. Bootstrap manually with AGENTS.md if Steward CLI is not available.

What is a repository ecology review?▼

A repository ecology review inspects plans, docs, ADRs, skills, schemas, tools, and evidence surfaces to assign explicit dispositions such as keep, compress, merge, update, remove, create, defer, or move to check. It prefers a single disposition table over creating new doctrine pages.

When should I not use this repo quality skill?▼

Do not use it for writing product or domain features directly, creating or packaging an Agent Skill, or maintaining an existing steward.yaml action contract. Those tasks route to product skills, skill-authoring-lifecycle, or mcp-harness-repo-maintainer respectively.

How does the skill prove repository maturity claims honestly?▼

It uses the weakest true claim rather than the strongest desired one, recording claim tier, owner, evidence, validation command, falsifier, and non-claims. Blocked checks, skipped generators, and green Steward-only ledgers without product deltas are labeled as support, not product acceleration.

Can this skill handle multi-repo producer and consumer integrations?▼

Yes. It records dependency order, source-of-truth repo, consumer gate, and do-not-touch exceptions. The producer repo owns architecture, public contract, and release provenance, while consumer repos own adoption proof, local deltas, and cutover commands.