claude-skills-mcp-dev
Private dev repo for the
active-claude-github
Claude Code skill's MCP server. Consumer docs live at the publish
target: https://codeberg.org/telejester-skills/telejester-claude-skills.
This repo is where MCP server development happens — Issues, Discussions, CI, Bazel build graph, tests. Releases are published to the publish-target repo linked above.
What lives here
- Python package
active_claude_github_mcp/implementing the MCP tool surface. tests/— Bazel-orchestrated unit and integration tests in two layers: helper-level (#79, ephemeral repos) and tool-level (#89, persistent fixture repo attelejester-test-org/integration-fixture). SeeCONTRIBUTING.mdfor the build and test conventions and §Persistent fixture repo for the provisioning protocol..github/workflows/— CI (bazel test+bazel coverageon every PR;workflow_dispatchlive-GitHub integration tests).- Issues / Discussions / Project board cross-referenced with the skill dev repo at https://github.com/orgs/telejester-claude-skills/projects/1.
Bootstrapping a new project
scaffold_project is the MCP tool that stands up a new managed project
end-to-end: creates the <org>/<name> public + <org>/<name>-dev
private repo pair, seeds the standard label set, enables Discussions on
the dev repo, creates a ProjectV2 board (linked to both repos) with the
canonical Backlog → In Progress → In Review → Done / Parked Status
field, seeds the Project and Session-Lock Discussions, and writes
.claude/github-config.json with every resolved ID.
The tool is idempotent and pauses for exactly one manual step: creating
the five Discussion categories (Project, Architecture, UX / UI,
Ideas, claude-use-only) via the dev-repo's Settings page, which
GitHub exposes no API for. Re-run the tool once the categories exist
and it picks up where it left off.
The exact bootstrap flow — invocation, expected pauses, and follow-up
open_session — lives in the consumer skill's §Self-Bootstrap
Instructions: https://codeberg.org/telejester-skills/telejester-claude-skills.
Multi-repo relations (1.3.0+)
github-config.json accepts a related_repos list that tags each
connected repo with one of six relationship types. The server uses
these tags at dispatch time to gate cross-repo mutations per the
skill's §Cross-repo work protocol:
| Type | Gate |
|---|---|
subsystem, publish_target, sibling, neighbor |
Allowed |
cousin (different org, skill-managed) |
Blocked — requires explicit user permission per operation |
foreign (no write access) |
Blocked — treat as informational only |
Blocks surface as a non-buffered OperationError with manual_step
populated; no GitHub calls are issued. Unknown targets (not declared
in related_repos) pass through — the preflight doesn't invent
policy for undeclared repos.
The pre-1.3.0 contribution_target type still parses for backward
compat but emits a DeprecationWarning at load. Migrate each entry
to its precise sub-type at next config edit.
Contributing
See CONTRIBUTING.md.
Related repos
- MCP server publish target (consumer-facing): https://codeberg.org/telejester-skills/telejester-claude-skills
- Skill (consumer-facing): https://codeberg.org/telejester-skills/telejester-claude-skills
- Skill dev repo: https://codeberg.org/telejester-skills/telejester-claude-skills-dev
License
Apache License 2.0 — © 2026 Telejester.
1 maintainer
Metadata
1 maintainer
Release files for forge-manager-mcp 4.16.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| forge_manager_mcp-4.16.3.tar.gz | 11.5 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| forge_manager_mcp-4.16.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.4 MB
Release files / forge_manager_mcp-4.16.3.tar.gz
| Download URL | forge_manager_mcp-4.16.3.tar.gz |
|---|---|
| Size | 11.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58a54fdfb73b935f913b47735ab80571df8cb520f8dbe675187cf1a59bdf6ba1
|
|
BLAKE2b-256 checksum How to use checksums |
d9c4fab501f690bab7d4823d62c8f7f3942bc4430b5b353bc0c66ab629e76002
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Release files / forge_manager_mcp-4.16.3-py3-none-any.whl
| Download URL | forge_manager_mcp-4.16.3-py3-none-any.whl |
|---|---|
| Size | 11.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
57d0e035d6114a918fd98ece8f67ab8375be89691d165d861282b98cfec93044
|
|
BLAKE2b-256 checksum How to use checksums |
976f5f0bd6d403a8695c6747d9da3d371048923311d9e39c8cdcd75aaa6f3835
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Security for forge-manager-mcp 4.16.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
