tool-project-config

Resolve org and project context from the git remote origin.

2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/simon-downes/archie --skill tool-project-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-project-config
Source: https://github.com/simon-downes/archie/tree/main/persona/skills/tool-project-config
Command: npx skills add https://github.com/simon-downes/archie --skill tool-project-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve the current project's configuration from the git remote and apply org/project-specific settings for providers, issues, and notifications.

Core Features & Use Cases

  • Determine the active org and project from git remote origin to drive per-project configuration.
  • Merge org-level defaults with per-project overrides so workflows can adapt to the current repository.
  • Gracefully handle when not in a git repository or when origin is missing, returning no config.

Quick Start

Start by resolving the current project context from the git remote to load the merged org/project configuration.

Frequently Asked Questions about tool-project-config

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

FAQPage Schema
How do I resolve project context from a git remote origin URL?

To resolve project context from a git remote, the system extracts the origin URL, derives the organization and project names, and merges project overrides with organizational defaults defined in your configuration file.

How do I apply organization-specific settings for git operations and notifications?

You can apply organization-specific settings by reading configuration files to merge org-level defaults with per-project overrides, allowing workflows to adapt to the current repository for routing and notifications.

What happens to project configuration if the git repository origin is missing?

When the git repository origin is missing, the configuration process gracefully handles the absence by returning no config, ensuring workflows do not break when project context cannot be resolved.

Can I merge project overrides with org defaults for provider routing?

Yes, you can merge project overrides with org defaults to determine which provider defaults apply for the current repository, enabling accurate org and project-specific routing.

When do I need to infer project context from git remote?

You need to infer project context from git remote when preparing git operations, issue tracking, or Slack notifications, and when skills need to determine which provider defaults apply for the current repository.

Does project configuration require a specific file format for org and project settings?

Project configuration requires a YAML file format, specifically reading from the projects.yaml file, to extract and merge organizational defaults with per-project overrides.