Documentation Guide
jmfederico/pi-web
Repository documentation placement and writing guidance. An agent skill from jmfederico/pi-web.
Master orchestration for repository governance, North Star impact, sub-Star boundaries, and repair-first or evidence-first drift checks.
Install Repository Governance Lifecycle
$ npx skills add Arenukvern/mcp_flutter --skill repository-governance-lifecycle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Arenukvern/mcp_flutter repository-governance-lifecycle --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Arenukvern/mcp_flutter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/repository-governance-lifecycle .claude/skills/repository-governance-lifecycle && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "repository-governance-lifecycle" agent skill from https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/repository-governance-lifecycle into .claude/skills/repository-governance-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repository-governance-lifecycle", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/repository-governance-lifecycleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Arenukvern/mcp_flutter --skill repository-governance-lifecycle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Arenukvern/mcp_flutter repository-governance-lifecycle --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Arenukvern/mcp_flutter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/repository-governance-lifecycle .agents/skills/repository-governance-lifecycle && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "repository-governance-lifecycle" agent skill from https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/repository-governance-lifecycle into .agents/skills/repository-governance-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repository-governance-lifecycle", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Arenukvern/mcp_flutter --skill repository-governance-lifecycle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Arenukvern/mcp_flutter repository-governance-lifecycle --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Arenukvern/mcp_flutter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/repository-governance-lifecycle .cursor/skills/repository-governance-lifecycle && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "repository-governance-lifecycle" agent skill from https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/repository-governance-lifecycle into .cursor/skills/repository-governance-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repository-governance-lifecycle", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Arenukvern/mcp_flutter.git --path .agents/skills/repository-governance-lifecycle--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Arenukvern/mcp_flutter --skill repository-governance-lifecycle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Arenukvern/mcp_flutter repository-governance-lifecycle --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Arenukvern/mcp_flutter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/repository-governance-lifecycle .gemini/skills/repository-governance-lifecycle && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "repository-governance-lifecycle" agent skill from https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/repository-governance-lifecycle into .gemini/skills/repository-governance-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repository-governance-lifecycle", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Arenukvern/mcp_flutter repository-governance-lifecycleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Arenukvern/mcp_flutter --skill repository-governance-lifecycle -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Arenukvern/mcp_flutter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/repository-governance-lifecycle .github/skills/repository-governance-lifecycle && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "repository-governance-lifecycle" agent skill from https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/repository-governance-lifecycle into .github/skills/repository-governance-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repository-governance-lifecycle", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Arenukvern/mcp_flutter --skill repository-governance-lifecycle -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Arenukvern/mcp_flutter repository-governance-lifecycle --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Arenukvern/mcp_flutter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/repository-governance-lifecycle .opencode/skills/repository-governance-lifecycle && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "repository-governance-lifecycle" agent skill from https://github.com/Arenukvern/mcp_flutter/tree/main/.agents/skills/repository-governance-lifecycle into .opencode/skills/repository-governance-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repository-governance-lifecycle", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
repository-governance-lifecycle- GitHub stars
- 387
- Token cost
- ~1.5k tokens
- SKILL.md length
- 718 words
- Files
- 13 (incl. references)
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- MIT
At a glance
Master orchestration for repository governance, North Star impact, sub-Star boundaries, and repair-first or evidence-first drift checks.
- Works in 6 steps: Check Ethics & Boundaries (NORTH_STAR) → Log the Decision (ADRs) → Update Living Docs (FAQs) → …
- You need to make a structural change
- SKILL.md covers The Governance Loop, Install and Sources
- Calls npx
What it does
Repository Governance Lifecycle is an agent skill from Arenukvern/mcp_flutter. Master orchestration for repository governance, North Star impact, sub-Star boundaries, and repair-first or evidence-first drift checks. Guides an agent through the complete lifecycle of making architectural decisions, documenting them, writing FAQs, and cleaning up stale plans while adhering strictly to repo ethics and brand tone. Use whenever you need to make a structural change, write an ADR, update the doc lattice, or govern repository architecture.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files, including reference files (for example `evals/cases/evidence-routing-trigger.yaml`, `evals/cases/governance-adr-trigger.yaml` and `evals/cases/logo-work-dormant.yaml`).
It sits in Development, covering Architecture decision records and Help center and FAQ content. The repository describes itself as: MCP Toolkit for Flutter AI Agent Driven Development (MCP/CLI + custom client side tools) - via closed feedback loop (visual & semantic snapshot) and high client side… The licence is MIT.
When your agent uses it
- You need to make a structural change
- Update the doc lattice
- Govern repository architecture
Example prompts
- “/repository-governance-lifecycle”
Requirements
- Node.js
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 62f3ee1. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Repository Governance Lifecycle loads about 1.5k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 122 tokens; SKILL.md has 718 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Arenukvern/mcp_flutter at commit 62f3ee1, republished under its MIT licence (© Arenukvern). 718 words, ~1,542 tokens.
Download SKILL.mdSave it as
.claude/skills/repository-governance-lifecycle/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.- name
- repository-governance-lifecycle
- description
- Master orchestration for repository governance, North Star impact, sub-Star boundaries, and repair-first or evidence-first drift checks. Guides an agent through the complete lifecycle of making architectural decisions, documenting them, writing FAQs, and cleaning up stale plans while adhering strictly to repo ethics and brand tone. Use whenever you need to make a structural change, write an ADR, update the doc lattice, or govern repository architecture.
- license
- MIT
- type
- governance
- metadata.author
- skill-steward
- metadata.version
- 1.1.0
- metadata.category
- governance
Repository Governance Lifecycle
This is the central nervous system for governing an agent-operated repository. It applies to apps, libraries, tools, plugins, harnesses, and meta repos; Skill Steward itself remains a structural stewardship repo, not a domain tutorial catalog. It unifies ethics, branding, architectural decision logs (ADRs), and living documentation (FAQs) into a single, cohesive loop: Decide → Document → Cleanup.
Whenever an agent proposes or executes a structural shift, claim change, durable policy change, or docs-lattice change, they must walk this loop. Routine repo repairs should keep the original goal and native gate first; use this governance loop only when the repair changes durable ownership, policy, evidence, ADR/FAQ truth, or plan hygiene.
The Governance Loop
1. Check Ethics & Boundaries (NORTH_STAR)
Before making any decision, check the repository's foundational charter and ethical baseline.
- Read Charter and Ethics to ensure your proposed changes do not violate the repository's moral boundaries (e.g. no hype; no domain tutorials inside Skill Steward; domain docs belong in the governed product repo when they are that repo's product).
- Read North Star Rules to understand the extension model.
- Classify
north_star_impactfor durable structural changes:none,applies,clarifies,sub_star,amends, orconflicts. Use the protocol only when ownership, policy, evidence truth, ADR/FAQ truth, or the repo's center may change. - Ask the gate questions before editing durable governance surfaces: what pain triggered this; which North Star value path it serves; whether it is a mechanism or a new center; whether it changes what the repo owns or refuses; where the ADR is if it does; and what check prevents the mechanism becoming the mission if it does not.
- Route
noneandappliesthrough the native workflow,clarifiesthrough FAQ/skill/map/check updates,sub_starthrough an explicit parent/child boundary, andamendsorconflictsthrough an ADR plus a North Star diff before implementation.
2. Log the Decision (ADRs)
If you have made an architecturally significant decision (or triggered a T1-T8 threshold), you must write it down. Decisions are not valid if they only live in an agent's context window.
- Follow the formatting rules in ADR Format to write a formal Decision Record.
3. Update Living Docs (FAQs)
Decisions change how the repository operates day-to-day. You must update the living system of record.
- Update
docs/DESIGN_FAQ.mdx(the Why) ordocs/DX_FAQ.mdx(the How). - Follow the exact structuring rules in FAQ Format to ensure questions are searchable and direct.
4. Apply Brand & Tone Identity
When writing ADRs, FAQs, or any user-facing documentation, you must adhere strictly to the repository's tone.
- Do not use corporate marketing jargon.
- Review the banned word list in Brand Guidelines (e.g. do not use "unlock", "supercharge", "ultimate").
Show full SKILL.md (286 more words)Show less
5. Plan Hygiene (Cleanup)
Never leave stale planning artifacts (task.md, implementation_plan.md) as permanent documentation.
- Once the ADR and FAQs are updated, your knowledge is durable.
- Extract any remaining useful context and delete or ignore the scratch files.
- For stale or overlapping non-plan docs, choose one disposition before editing: keep, merge, move to ADR, move to FAQ, move to skill, move to check, move to evidence, move to consumer proof, or delete.
- Ask what existing doc can shrink or disappear because of this change.
- Keep canonical architecture in the owning repo; consumer repos should carry adoption proof, local deltas, blocked state, and links to the owner.
- For broader surface-shape decisions such as split, compress, promote, demote, delete, or stay native, route through repo-quality-system-lifecycle and Evolutionary simplicity instead of inventing a governance-only doctrine.
- Before upgrading steward, adoption, harness-ready, or maturity language in an ADR/evidence note, run
steward claim check --claim <claim> --evidence <path> --json. Treatnot_rejectedas a negative-gate result, not acceptance.
6. Route Evidence Deliberately
Do not turn every run, plan, or discussion into evidence. Use Evidence artifacts as the routing rule:
- ADR: durable decision, trade-off, status, or consequence.
- FAQ: standing why/how that humans and agents will ask again.
- Skill: repeatable agent procedure or interpretation loop.
- Check/tool/schema/test: deterministic drift, freshness, shape, or blocked-state detection.
- Current ledger: weakest true current status and rerun route.
- Evidence artifact: real run proof, blocked state, pattern review, PDSA loop, postmortem, unknown case, or reference that protects a claim or changes future behavior.
- Delete/remove: completed checklist, stale plan, or template once useful truth has been extracted.
When you create or materially update an evidence artifact, use the canonical envelope in Evidence artifacts. ADR 0023 explains why that envelope exists.
Install
npx skills add arenukvern/skill_steward --skill repository-governance-lifecycleSources
© Arenukvern, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 12 other files (references) in .agents/skills/repository-governance-lifecycle of Arenukvern/mcp_flutter.
- SKILL.md
- evals/cases/evidence-routing-trigger.yaml
- evals/cases/governance-adr-trigger.yaml
- evals/cases/logo-work-dormant.yaml
- evals/cases/north-star-impact-trigger.yaml
- evals/cases/routine-repair-dormant.yaml
- references/adr-format.md
- references/brand-guidelines.md
- references/charter-and-ethics.md
- references/evals.md
- references/faq-format.md
- references/north-star-rules.md
- references/sources.md
Open the folder on GitHubat commit 62f3ee1
Compare with similar skills
Repository Governance Lifecycle next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Repository Governance Lifecycle this skillArenukvern/mcp_flutter | 387 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Documentation Guidejmfederico/pi-web | 871 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Dev Rfcpproenca/dot-skills | 215 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Triangulate Spec ReviewQoderAI/better-harness | 2.4k | — | ~614 | Automated safety check: Pass | MIT | |
| Funboost Troubleshootingydf0509/funboost | 895 | — | ~2.2k | Automated safety check: Pass | None | |
| PR Design DocOpenHands/OpenHands | 91k | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
Dev Rfc
pproenca/dot-skills
Create well-structured RFCs and technical proposals for software projects.
Triangulate Spec Review
QoderAI/better-harness
Review and improve architecture specs, ADRs, plugin or agent directory proposals, and other design documents by running multiple independent AI reviewers such as Claude, Qoder, Codex, or Cursor…
Funboost Troubleshooting
ydf0509/funboost
当使用 funboost 遇到错误、消费不正常、进程退出等问题时使用。触发场景：消费者不启动、消息不消费、进程卡死、event loop 报错、日志不输出、PYTHONPATH 问题、Ctrl+C 无法退出。关键词：troubleshooting, FAQ, 排错, 调试, PYTHONPATH, runforever, Ctrl+C, event loop, 日志。
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
More from Arenukvern/mcp_flutter
All 23 skills in this repoHarness Engineering Lifecycle
Arenukvern/mcp_flutter
Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists.
Mixture Of Experts
Arenukvern/mcp_flutter
Run a Mixture of Experts (MoE) audit on any topic, plan, codebase, evidence archive, or process.
Multi Agent Handoff
Arenukvern/mcp_flutter
Plan and document handoffs, parent lane contracts, and parallel batch contracts between specialized AI agents (foreman, workers, reviewers).
Plugin Marketplace Setup
Arenukvern/mcp_flutter
Designs public or private Agent Skill and plugin marketplaces for Cursor, Claude Code, Codex, Zed, Open Plugin, and npx skills—manifest layout, install matrix, and Skill Steward vs product boundaries.
Release Changelog Harness
Arenukvern/mcp_flutter
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable.
Skill Authoring Lifecycle
Arenukvern/mcp_flutter
Scaffold and formally review a new Agent Skill in this marketplace repo.
Related
Categories
Questions about Repository Governance Lifecycle
What does Repository Governance Lifecycle do?
Master orchestration for repository governance, North Star impact, sub-Star boundaries, and repair-first or evidence-first drift checks. Repository Governance Lifecycle is an agent skill from Arenukvern/mcp_flutter. Master orchestration for repository governance, North Star impact, sub-Star boundaries, and repair-first or evidence-first drift checks.
When should I use Repository Governance Lifecycle?
Repository Governance Lifecycle fits situations like: you need to make a structural change; update the doc lattice; govern repository architecture.
How do I install Repository Governance Lifecycle in Claude Code?
Run `npx skills add Arenukvern/mcp_flutter --skill repository-governance-lifecycle -a claude-code`. Or copy the skill folder (.agents/skills/repository-governance-lifecycle in Arenukvern/mcp_flutter) into .claude/skills/repository-governance-lifecycle in your project. Claude Code loads it when a task matches its description.
How do I install Repository Governance Lifecycle in Codex?
Run `npx skills add Arenukvern/mcp_flutter --skill repository-governance-lifecycle -a codex`. Or copy the skill folder (.agents/skills/repository-governance-lifecycle in Arenukvern/mcp_flutter) into .agents/skills/repository-governance-lifecycle in your project. Codex loads it when a task matches its description.
Can I use Repository Governance Lifecycle in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Arenukvern/mcp_flutter --skill repository-governance-lifecycle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/repository-governance-lifecycle, .gemini/skills/repository-governance-lifecycle, .github/skills/repository-governance-lifecycle and .opencode/skills/repository-governance-lifecycle in your project.
What does Repository Governance Lifecycle need to run?
Going by SKILL.md and its folder, Repository Governance Lifecycle needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Repository Governance Lifecycle access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Repository Governance Lifecycle safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Repository Governance Lifecycle use?
Repository Governance Lifecycle is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Repository Governance Lifecycle use?
About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.2k tokens, read only when the agent opens those files.
What are the alternatives to Repository Governance Lifecycle?
Skills that share tags, products or a category with Repository Governance Lifecycle: Documentation Guide (jmfederico/pi-web, 871 stars), Dev Rfc (pproenca/dot-skills, 215 stars), Triangulate Spec Review (QoderAI/better-harness, 2.4k stars) and Funboost Troubleshooting (ydf0509/funboost, 895 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Repository Governance Lifecycle?
Arenukvern (a GitHub user) maintains it in Arenukvern/mcp_flutter, which has 387 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 3, 2026.
Source: Arenukvern/mcp_flutter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.