agent-context

This repository is the GitHub template repo for intel-agency: the substrate from which each downstream instance is cloned to house a unique application plan and develop it. Any other repo name is a clone instance seeded from this one.

Prerequisites

• PowerShell 7+ (pwsh) — all scripts in this repo are written in cross-platform PowerShell.

• GitHub CLI (gh) — authenticated with repo, project, and user:email scopes. Verify with:

  gh auth status

• Node.js (optional) — only needed to run markdownlint-cli2 for Markdown linting.

Getting started

1. Create a new repository from this template (or clone it).
2. Ensure all environment variables are set in your shell.
3. Read AGENTS.md — the operating manual for AI agents working in this repo.
4. Consult .agents/memory.md for project history and current state.

Configuration

Environment variables are documented in docs/environment-variables.md. Secrets are referenced as {env:VAR} patterns in .opencode/opencode.jsonc and are never committed to the repository.

Repository layout

Path	Description
AGENTS.md	Operating manual for AI agents (coding guidelines, validation, source control)
.agents/memory.md	Durable project context: current activity, completed work, decisions
.agents/rules/	Coding conventions, tool usage, validation, and practices (one file per subject)
.agents/skills/	Agent Skills (gh-issue-tracking-init, update-powershell-standard)
docs/	Reference documentation including environment variables
scripts/	GitHub CLI helpers: auth, label sync, PR review-thread management, index refresh
local_ai_instruction_modules/	Workflow assignment and dynamic workflow lookup tables
.opencode/	OpenCode agent definitions and runtime configuration

Running the tests

The Pester test suite covers the gh-issue-tracking-init skill scripts:

Invoke-Pester -Path .agents/skills/gh-issue-tracking-init/scripts/tests -Output Detailed

Expected result: 101 tests passing across three test files (GhIssueTracking, SetProjectFields, AssertNoSecrets).

Linting

Markdown linting uses markdownlint-cli2 with configuration in .markdownlint.json. Scope linting to changed files to avoid known pre-existing violations in docs/plans/new templates/ and local_ai_instruction_modules/:

markdownlint-cli2 README.md .agents/memory.md

Contributing

• Create a new branch for each change using the form <prefix>/<name> (e.g. dev/new-feature).
• Run /safe-commit before committing to scan for uncommitted secrets.
• Pull requests must have a milestone and project set. See .agents/rules/source-control.md for full details.

Where to look next

• AGENTS.md — start here for agent operating instructions.
• .agents/memory.md — project history and decisions.
• .agents/rules/ — detailed conventions for each subject area.