ar-install-context

Installs context-processing command templates into a Docs Project directory.

1|2|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/mahsanamin/agentic-repos --skill ar-install-context-mahsanamin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ar-install-context
Source: https://github.com/mahsanamin/agentic-repos/tree/main/.claude/commands/ar-install-context
Command: npx skills add https://github.com/mahsanamin/agentic-repos --skill ar-install-context-mahsanamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams maintaining documentation projects need consistent AI commands for processing discussions, emails, meeting minutes, specs, and project state, but manually copying and configuring these templates across projects leads to drift and inconsistency. ## Core Features & Use Cases - Template Installation: Copies six context-processing command templates (discussions, emails, meeting minutes, specs, state, document formatting) into a target Docs Project's .claude/commands/ and .claude/rules/ directories. - Automatic Path Derivation: Detects the repo root, base path, commands/rules directories, and archive path from a single docs project path, with user confirmation before writing. - Update-Safe Behavior: Always overwrites generic templates while skipping project-specific files (specs registry, state sections, formatting rules) to preserve local customizations. - Use Case: After updating the meeting-minutes template in the central agentic-repos repo, run this installer to push the new version to every Docs Project without touching their customized specs or state files. ## Quick Start Install the context skills into my Docs Project at ~/repos/example/Example_Docs_Project.

Frequently Asked Questions about ar-install-context

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

FAQPage Schema
How do I install context-processing commands into a Claude Code docs project?▼

Provide the absolute path to your Docs Project and the installer derives the repo root, base path, and archive location automatically. It writes six command templates into .claude/commands/ and one rule into .claude/rules/ after you confirm the derived paths.

How do I update context command templates across multiple projects?▼

Edit the templates in the central context-skills/templates/ directory, then re-run the installer for each target project. Generic templates are always overwritten, so updates propagate while project-specific files remain untouched.

Will updating overwrite my customized specs or state files?▼

No. The context-update-specs, state-update, and document-formatting files are skipped if they already exist, preserving project-specific content like your Document Registry. To force an update, delete the existing file first and re-run the installer.

Does this installer affect ar-taskflow skills or config?▼

No. It is completely independent of ar-taskflow and never reads or modifies skill.config, config_hints.json, hooks, or ar-* skills. It only installs context command templates and creates documentation directories.

What happens if no Archive directory exists in the repo?▼

The installer scans the repo root for a directory matching *Archive*. If none is found, it derives one by replacing DocsProject or Docs_Project with Archive in the parent directory name and creates it automatically.