Welcome to afwf_home_documents_github Documentation
An Alfred workflow for indexing and acting on repos under ~/Documents/GitHub.
All of the user’s git repos are backed up as top-level folders directly under ~/Documents/GitHub. Every feature in this workflow starts from the same place: pick a top-level repo folder under that root, then do something with it. Today there are two keywords:
files — search for any file or folder inside the selected repo, then open it or reveal it in Finder.
ccc — open a new terminal tab in the selected repo and start a Claude Code session there.
For how each keyword works end-to-end, and the tools it depends on, see the “How the Workflow Works” section in the full documentation.
Install
This package is not on PyPI yet — it’s used locally as the CLI that backs this Alfred workflow’s Script Filter nodes (see info.plist). Clone the repo and install it into its own virtual environment:
$ mise run instThat installs the afwf-home-documents-github console script into .venv/bin/, which each Script Filter node calls directly during development. Once this is published to PyPI, the usual install will also work:
$ pip install afwf-home-documents-githubTo upgrade to latest version:
$ pip install --upgrade afwf-home-documents-github1 maintainer
Metadata
1 maintainer
Release files for afwf_home_documents_github 0.1.1
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 | Actions |
|---|---|---|---|---|
| afwf_home_documents_github-0.1.1.tar.gz | 16.0 kB | Without provenance | Details for afwf_home_documents_github-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| afwf_home_documents_github-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for afwf_home_documents_github-0.1.1-py3-none-any.whl |
Total release size: 29.8 kB
Release files / afwf_home_documents_github-0.1.1.tar.gz
| Download URL | afwf_home_documents_github-0.1.1.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4dfa724fb7fb5150a88b6353ac486ce176a1636bfc205e52bf41ff3a9331f8e5
|
|
BLAKE2b-256 checksum How to use checksums |
ece6ad37fa797c58d9521bba4f8e1ffe20f64d25224328713249b91c08750a1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / afwf_home_documents_github-0.1.1-py3-none-any.whl
| Download URL | afwf_home_documents_github-0.1.1-py3-none-any.whl |
|---|---|
| Size | 13.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a06c8a2f691dab4ce8c87e2be2c2b957a0dff65721e8b53cec66e90b7a4cb73
|
|
BLAKE2b-256 checksum How to use checksums |
2253864a3de90fc900d1a0aad10d550ddcf0fa69198e9c4f042a7cacd988e446
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for afwf_home_documents_github 0.1.1
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.
