一键在 Manus 中运行任何 Skill

darwin-repo-context

星标7

分支1

更新时间2026年6月3日 11:11

Discover and load project-specific AI context from cloned repositories. Activates when cloning or pulling a repository to check for .gemini, .claude, or .cursor configuration directories.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

The-Darwin-Project

The-Darwin-Project/Blackboard

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Repository Context Discovery

When to Use

After cloning or pulling any repository, ALWAYS check for project-specific AI context before starting work. Repositories may contain rules, skills, memory files, and conventions that override or extend your default behavior.

Discovery Steps

After git clone or git pull, check for these directories in the repo root:

.gemini/ -- Gemini CLI context
- GEMINI.md -- Project memory and conventions (read this first)
- settings.json -- Workspace settings
- skills/ -- Project-specific skills
- .geminiignore -- Files to exclude from context
.claude/ -- Claude Code context
- CLAUDE.md -- Project memory and conventions (read this first)
- settings.json -- Workspace settings
- skills/ -- Project-specific skills
- agents/ -- Custom subagent definitions
.cursor/ -- Cursor IDE context
- rules/ -- Project-specific rules (*.mdc files or markdown)
- skills/ -- Project-specific skills
- plans/ -- Existing plans for this project

What to Do

After cloning, check for context directories (.gemini/, .claude/, .cursor/) and read their main context files (GEMINI.md, CLAUDE.md) and any rules directories.

How to Use What You Find

Memory files (GEMINI.md, CLAUDE.md): These contain project conventions, architecture decisions, and constraints. Follow them as if they were part of your agent rules.
Skills: Project-specific skills may extend or override your Darwin skills. Note their existence in your report.
Rules: Project rules define coding standards, naming conventions, and forbidden patterns. Respect them.
Plans: Existing plans may provide context for the current task. Check if the work was previously planned.

Rules

ALWAYS check for context files. This is not optional.
Read context files BEFORE making any changes to the repository.
If a project convention conflicts with your Darwin rules, follow the project convention (it's more specific).
Report what context files you found in your team_send_message status updates so FRIDAY knows the repo is self-documenting.

同仓库更多 Skills

同仓库

darwin-dockerfile-safety

The-Darwin-Project/Blackboard

Safety rules for modifying Dockerfiles and Containerfiles. Use when editing container build files.

2026-07-217

darwin-reporting-context

The-Darwin-Project/Blackboard

MR/PR context gathering and diagnostic reporting guidelines. Activates when working on events that reference MRs/PRs or when reporting investigation findings.

2026-07-217

darwin-team-huddle

The-Darwin-Project/Blackboard

Team coordination for implement and test modes. Developer and QE use team_send_results for final reports, team_huddle for mid-task questions to FRIDAY.

2026-07-217

darwin-gitops

The-Darwin-Project/Blackboard

GitOps workflow rules for modifying infrastructure via git. Use when cloning repos, modifying Helm values, committing, pushing, or verifying deployments.

2026-07-137

darwin-mr-lifecycle

The-Darwin-Project/Blackboard

MR/PR lifecycle operations -- pipeline check, retest, merge, conflict reporting. Extends darwin-gitlab-ops.

2026-07-137

darwin-comms

The-Darwin-Project/Blackboard

Report findings and status updates to the Darwin FRIDAY. Use team_send_results for final reports (task modes). In message mode, use team_send_message instead.

2026-07-097

name	darwin-repo-context
description	Discover and load project-specific AI context from cloned repositories. Activates when cloning or pulling a repository to check for .gemini, .claude, or .cursor configuration directories.
roles	["architect","sysadmin","developer","qe"]

Repository Context Discovery

When to Use

Discovery Steps

After git clone or git pull, check for these directories in the repo root:

.gemini/ -- Gemini CLI context
- GEMINI.md -- Project memory and conventions (read this first)
- settings.json -- Workspace settings
- skills/ -- Project-specific skills
- .geminiignore -- Files to exclude from context
.claude/ -- Claude Code context
- CLAUDE.md -- Project memory and conventions (read this first)
- settings.json -- Workspace settings
- skills/ -- Project-specific skills
- agents/ -- Custom subagent definitions
.cursor/ -- Cursor IDE context
- rules/ -- Project-specific rules (*.mdc files or markdown)
- skills/ -- Project-specific skills
- plans/ -- Existing plans for this project

What to Do

After cloning, check for context directories (.gemini/, .claude/, .cursor/) and read their main context files (GEMINI.md, CLAUDE.md) and any rules directories.

How to Use What You Find

Memory files (GEMINI.md, CLAUDE.md): These contain project conventions, architecture decisions, and constraints. Follow them as if they were part of your agent rules.
Skills: Project-specific skills may extend or override your Darwin skills. Note their existence in your report.
Rules: Project rules define coding standards, naming conventions, and forbidden patterns. Respect them.
Plans: Existing plans may provide context for the current task. Check if the work was previously planned.

Rules

ALWAYS check for context files. This is not optional.
Read context files BEFORE making any changes to the repository.
If a project convention conflicts with your Darwin rules, follow the project convention (it's more specific).
Report what context files you found in your team_send_message status updates so FRIDAY knows the repo is self-documenting.